mcp-usage contradicts itself on why an analyze parameter is missing
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- shell
- Domain
- documentation
Research direction
Read skills/mcp-usage/SKILL.md, focusing on “When this guidance and the server disagree” and the advancedRules section. Make the guidance consistent so entitlement is concluded only after confirming the running server version supports the documented feature. Done when the conflicting rules are reconciled and the plugin’s pinned server version remains unchanged.
Written by the indexing model from the issue text.
Description
Problem
skills/mcp-usage/SKILL.md gives agents two conflicting rules for a parameter (such as advancedRules or igtTools) that the skill documents but the server's analyze schema doesn't advertise:
- The "When this guidance and the server disagree" section says absence "means the account is not entitled to it, not that the server is old."
- The
advancedRulessection says to "rule out a stale server before concluding it is entitlement" by checkingserverInfo.versionagainst the feature's minimum version.
An agent following the first rule tells a user on an old server (for example a Docker config still on an older tag) that their account lacks an entitlement, when upgrading the server would fix it.
Acceptance criteria
- The skill gives one consistent rule: a documented parameter missing from the schema is attributed to entitlement only after the running server version is confirmed to support the feature.
Non-goals
- Changing which server version the plugin pins.
Affected contracts
Changes customer agents' guidance when a documented parameter is missing.
- Dominant language
- Shell
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dequelabs/axe-accessibility
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dequelabs/axe-accessibility#9 · 2 comments · 1 reaction · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 57/100
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in dequelabs/axe-accessibility
Similar issues
-
bug report-to-upstream
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
flatpark/flatpark#1424 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[bug] Docker Compose version check in auto-install.sh fails on non-Debian systems (dpkg not found)Possibly taken @shaneintentionboi06 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openwisp/docker-openwisp#771 ·
Maintainers usually reply within 1 day
-
needs-you
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
catalystneuro/encore#860 ·
Maintainers usually reply within 1 day
-
Update crush to 0.102.0Possibly taken @zen0bit claimed this today. Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
oSoWoSo/oco#1251 · 1 comment ·
Maintainers usually reply within 1 day