Skip to main content
Glama
mcp-protocol-conformance

mcp-protocol-conformance

compareManifests

Read-onlyIdempotent

Diff two tool manifests to identify added, removed, and changed tools, so you can verify conformance between expected and actual MCP server definitions.

Instructions

Diff two tool manifests — added/removed/changed tools.

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": {
      "expected": "<expected>",
      "actual": "<actual>"
    },
    "name": "compareManifests"
  }
}

Input Schema

NameRequiredDescriptionDefault
actualYes
expectedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / actual / additionalProperties
      Removed value: -false
    • removedInput schema / properties / actual / properties / tools / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / actual / properties / tools / items / properties / _meta / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / actual / properties / tools / items / properties / annotations / additionalProperties
      Removed value: -false
    • removedInput schema / properties / expected / additionalProperties
      Removed value: -false
    • removedInput schema / properties / expected / properties / tools / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / expected / properties / tools / items / properties / _meta / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / expected / properties / tools / items / properties / annotations / additionalProperties
      Removed value: -false
  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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered structurally. The description adds the useful fact that results are bucketed into added/removed/changed, but says nothing about comparison depth (which fields are compared — title, description, inputSchema, _meta?), whether tool order matters, or how nested schema differences are reported.

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 compact sentence that front-loads the operation and the resource, with the output categories appended. Nothing redundant.

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, nested object parameters, and zero schema description coverage, the description is too thin for the tool's complexity: return shape (counts? per-tool detail? paths to changed fields?) and diff direction are both left to inference. The core promise is clear but the operational details an agent needs to use the result are missing.

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 two required parameters are deep nested manifest objects, so the description carries the burden — and it doesn't. Critically, it never establishes the direction of the diff: whether "added" means present in actual but absent from expected. An agent can guess that expected is the baseline, but the description does not say so.

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 uses a specific verb ("Diff") on a specific resource ("two tool manifests") and enumerates the result categories (added/removed/changed), so an agent can tell this is a comparison utility rather than a test runner like the sibling run* tools. It stops short of naming a sibling to distinguish itself from, notably assertNoBreakingChanges, which sounds closely related.

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 statement of when to reach for this versus alternatives, despite a sibling (assertNoBreakingChanges) that plausibly performs an overlapping manifest comparison. No prerequisites, no note about whether the tool fails on differences or merely reports them.

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