Skip to main content
Glama
mcp-protocol-conformance

mcp-protocol-conformance

runAnnotationsAudit

Read-onlyIdempotent

Audits all advertised MCP tools for annotation problems by applying destructive-name regex and readOnlyHint conflict rules to support protocol conformance checks.

Instructions

Apply the heuristic annotation rules (destructive name regex, readOnlyHint conflicts) to every advertised tool.

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

Input Schema

NameRequiredDescriptionDefault
targetYes
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.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral content by naming the two heuristic rule families it evaluates. However, it does not say whether violations cause a failure, what severity model applies, or what is returned, which a reader of an audit tool needs.

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 the scope constraint ('every advertised tool') is stated early. It is arguably too terse for the schema complexity it fronts, but nothing is wasted.

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, no parameter descriptions, and a required polymorphic target, the description should explain the connection mode and the result shape. It covers only the rule content, leaving an agent unable to construct the target argument from the definition alone.

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 required 'target' parameter is a oneOf union of a stdio command spec and an HTTP URL spec with no documented fields. The description says nothing about how to supply a target (command/args/env vs url/headers) or what specVersion changes, so it fails to compensate for a complex, undocumented required parameter.

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 states a specific action ('apply the heuristic annotation rules') and target scope ('every advertised tool'), and names the two checks it performs (destructive name regex, readOnlyHint conflicts). It is clear what the tool does, though it never explicitly says the 'target' must be an MCP server connection, nor does it differentiate itself from sibling checks like runToolSchemaValidation.

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 run this versus the many sibling audits (runToolSchemaValidation, runCapabilityIntrospection, runFullSuite). No prerequisites, no ordering advice, and no statement of what happens if violations are found.

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