Skip to main content
Glama
mcp-protocol-conformance

mcp-protocol-conformance

runTransportSuite

Read-onlyIdempotent

Verify an MCP server's transport layer over stdio line-delimited JSON or Streamable HTTP, helping confirm protocol conformance for the chosen target and spec version.

Instructions

Verify the target's transport layer (stdio line-delimited JSON or Streamable HTTP).

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": "runTransportSuite"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
transportNoboth
specVersionNo2025-06-18

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

C2.7/5.0
Behavior2/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 the safety profile is supplied. The description adds nothing beyond that: it does not say what 'verify' entails, whether subprocesses or network connections are actually made, what a failure looks like, or whether the check is passive or involves repeated probing. Notably, a tool that can spawn an arbitrary command or hit an arbitrary URL is arguably more open-world than openWorldHint=false implies, and the description does nothing to clarify that boundary.

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?

A single front-loaded sentence with no filler and no repetition. It is efficient, though its brevity is partly the source of the gaps above rather than a virtue in itself.

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?

With no output schema and a nested oneOf target (stdio cmd/args/env/cwd versus http url/headers) plus an undated specVersion enum, the description is far too thin to call this tool correctly. An agent cannot tell what result to expect, how the target shape pairs with the transport filter, or which spec version matters.

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% across three parameters, so the description must compensate and does not. It gestures at the two transport kinds via the parenthetical, but never explains the 'transport' param's 'both' default, the interaction between target.kind and transport, or what 'specVersion' selects among the four dated protocol versions.

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 gives a specific verb ('Verify') and resource ('the target's transport layer') and names the two transport modes covered, so an agent knows what is being probed. It does not differentiate itself from close siblings such as runJsonRpcCompliance or runRoundtripSmoke, which also exercise a live target, leaving scope overlap unresolved.

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 guidance on when to prefer this over the ten sibling run* checks, nor on prerequisites (does the target need to be reachable, does it spawn a subprocess?). The description also does not explain when to choose this single transport check versus runFullSuite, which presumably bundles it.

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