Skip to main content
Glama
mcp-protocol-conformance

mcp-protocol-conformance

runSpecVersionAssertion

Read-onlyIdempotent

Drive an initialize handshake against a target MCP server and assert that it advertises the expected spec version.

Instructions

Drive an initialize handshake and assert the target advertises the expected MCP spec version.

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>",
      "expectedVersion": "<expectedVersion>"
    },
    "name": "runSpecVersionAssertion"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
expectedVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / 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/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and openWorld=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact: it initiates a live handshake, i.e. it will spawn a stdio process or open an HTTP connection to the target. It does not disclose what happens on a version mismatch (throw, return a report, timeout behavior).

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

Conciseness5/5

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

A single front-loaded sentence with the action and its assertion outcome stated up front, and zero filler. Appropriately sized for a two-parameter assertion tool.

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?

There is no output schema, so the description should carry the result semantics, but it never says whether success is signaled by a returned value, an exception on mismatch, or a structured diff. Combined with the undescribed dual-mode target parameter, the definition leaves too much for the agent to guess.

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 target parameter is a non-trivial oneOf between a stdio object (cmd, args, cwd, env) and an HTTP object (url, headers). The description alludes to 'target' and 'expected version' but never explains that both a local process and a remote URL are accepted, so it fails to compensate for the schema's own lack of descriptions.

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 pairs a specific verb with a specific resource: it drives an initialize handshake and asserts the advertised MCP spec version. That clearly separates it from siblings such as runCapabilityIntrospection or runFullSuite. It stops short of naming a sibling boundary explicitly, so a 4 rather than a 5.

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

Usage Guidelines2/5

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

There is no stated guidance on when to reach for this narrow version check versus runFullSuite, runCapabilityIntrospection, or the other suite runners, and no preconditions or exclusions. The agent must infer its place in the test suite from the name alone.

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