Skip to main content
Glama
mcp-protocol-conformance

mcp-protocol-conformance

assertNoBreakingChanges

Read-onlyIdempotent

Compare baseline and current FullReport data to detect breaking changes and warnings, helping prevent incompatible MCP server updates.

Instructions

Compare a baseline FullReport against a current FullReport. Returns a list of breaking changes and warnings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "assertNoBreakingChanges"
  }
}

Input Schema

NameRequiredDescriptionDefault
currentNo
baselineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.2.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is covered. The description adds that the result is a list of breaking changes plus warnings, which is genuinely useful given there is no output schema, but it leaves a key ambiguity: despite the name 'assert', it is unclear whether breaking changes cause a failure/throw or are only reported.

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 short sentences with the action and the return value front-loaded and no filler. Brevity is fine; the gaps are omissions of content rather than wasted wording.

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

Completeness3/5

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

For a two-input comparison tool with no output schema and no annotations gap, the description covers the essentials but omits how to obtain FullReports, the result's structure beyond 'list', and the failure semantics implied by 'assert'. These are the details an agent would actually need to chain this tool correctly.

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

Parameters3/5

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

Schema coverage is 0% and the properties are untyped empty objects, so the description carries the burden of explaining the parameters. It does establish that both 'baseline' and 'current' are FullReport objects and what roles they play, but it says nothing about ordering, shape, or why required is empty when both inputs are obviously needed.

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 resource: compare a baseline FullReport against a current FullReport and return breaking changes and warnings. That is clear enough to act on, but it never distinguishes itself from the sibling compareManifests (or generateReport, which presumably produces the FullReports), so an agent cannot tell from the description alone which comparison tool to pick.

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 when-to-use guidance, no exclusion of alternatives, and no mention of where the two FullReport inputs come from. An agent must guess whether this belongs in a release gate, a pre-merge check, or after generateReport.

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