mcp-usage contradicts itself on why an analyze parameter is missing

Open Beginner friendly
#32 0 comments 0 reactions 0 assignees View on GitHub

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 advancedRules section says to "rule out a stale server before concluding it is entitlement" by checking serverInfo.version against 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dequelabs/axe-accessibility

All issues in dequelabs/axe-accessibility

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.