Keep interactions consistent with client requirements

A Tool interaction example can contradict its explicit minimum client requirements. Review the warning against the scenario and the declared requirements. The example does not automatically create or strengthen a client requirement.

Requirement

Interaction steps do not contradict the Tool’s explicit client capability requirements.

Details

Rule ID: mcpdesc.tool.interaction.client-requirements-consistency
Owner: mcpdesc
Surface: Tool interaction example · Path: steps
Kind: mcpdesc-semantic
Requirement level: should
Status: internal · Enforcement: internal

Protocol version applicability

2024-11-05	2025-03-26	2025-06-18	2025-11-25	2026-07-28
applies	applies	applies	applies	applies

Required by

• MCP Description 0.9.0, Sections 8.5 and 9.4
  • 9. Tools: req-interaction-client-requirements-warning

Notes

Steps never create requirements; the warning reports a contradiction only.

Examples

Accepted with a warning

Source: expected-warning/tool-interaction-client-requirements-contradictions.json · Selected: /tools/0/interactionExamples/contradictory/steps/0

{
  "type": "roots",
  "request": {},
  "response": {
    "roots": [
      {
        "uri": "file:///workspace/example"
      }
    ]
  }
}

Rule Source Code

interaction.yaml at immutable tag v0.9.0-rc.3.