Skip to main content
Glama
mcp-protocol-conformance

mcp-protocol-conformance

runToolSchemaValidation

Read-onlyIdempotent

Validate that every advertised MCP tool exposes a well-formed JSON-Schema inputSchema, and optionally diff the results against an expected manifest.

Instructions

Validate that every advertised tool has a well-formed JSON-Schema inputSchema. Optionally diff against an expected manifest.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "runToolSchemaValidation"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
specVersionNo2025-06-18
expectedManifestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / expectedManifest / additionalProperties
      Removed value: -false
    • removedInput schema / properties / expectedManifest / properties / tools / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / expectedManifest / properties / tools / items / properties / _meta / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / expectedManifest / properties / tools / items / properties / annotations / additionalProperties
      Removed value: -false
    • removedInput schema / properties / target / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "args": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "cmd": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "cwd": {
      -        "type": "string"
      -      },
      -      "env": {
      -        "additionalProperties": {
      -          "type": "string"
      -        },
      -        "type": "object"
      -      },
      -      "kind": {
      -        "const": "stdio",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "kind",
      -      "cmd"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "headers": {
      -        "additionalProperties": {
      -          "type": "string"
      -        },
      -        "type": "object"
      -      },
      -      "kind": {
      -        "const": "http",
      -        "type": "string"
      -      },
      -      "url": {
      -        "format": "uri",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "kind",
      -      "url"
      -    ],
      -    "type": "object"
      -  }
      -]
    • addedInput schema / properties / target / oneOf
      Added value: +[
      +  {
      +    "properties": {
      +      "args": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "cmd": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "cwd": {
      +        "type": "string"
      +      },
      +      "env": {
      +        "additionalProperties": {
      +          "type": "string"
      +        },
      +        "propertyNames": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      },
      +      "kind": {
      +        "const": "stdio",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "kind",
      +      "cmd"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "properties": {
      +      "headers": {
      +        "additionalProperties": {
      +          "type": "string"
      +        },
      +        "propertyNames": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      },
      +      "kind": {
      +        "const": "http",
      +        "type": "string"
      +      },
      +      "url": {
      +        "format": "uri",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "kind",
      +      "url"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. First observedv0.2.1

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered structurally. The description adds that validation operates over 'every advertised tool', but says nothing about how a target server is contacted, what happens on malformed schemas (fail vs report), or whether failures abort the run.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the primary action and no filler. The trailing 'Optionally diff against an expected manifest' is slightly vague but still earns its place by flagging the second mode.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This tool has a deeply nested, polymorphic target parameter, no output schema, and no parameter descriptions, so the description carries a heavy burden it does not meet. An agent knows what the tool checks but not how to construct a target, what specVersion affects, or what the result contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema is nested, with a oneOf between a stdio target (cmd/args/cwd/env) and an http target (url/headers), plus specVersion. The description never explains what 'target' accepts or that two transport shapes exist, only naming the optional manifest diff, so it leaves the most complex parameter entirely to the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and object ('Validate that every advertised tool has a well-formed JSON-Schema inputSchema'), which is concrete and actionable. It does not differentiate itself from sibling compareManifests or runAnnotationsAudit, even though the optional manifest diff overlaps with compareManifests, so an agent can't fully disambiguate the pair from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'Optionally' signals that expectedManifest is a conditional mode, which implicitly tells the agent when to supply it. However, there is no explicit statement of when to use this tool versus compareManifests, runAnnotationsAudit, or runFullSuite, and no prerequisites or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.