Skip to main content
Glama

Lexicon Garden

check_compatibility

Check compatibility between two versions of an ATProtocol lexicon schema. Detects breaking vs non-breaking changes and provides migration guidance. Supply either two schema JSON objects directly (from_schema + to_schema), or an NSID with two CIDs to compare stored versions (nsid + from_cid + to_cid).

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

Input Schema

NameRequiredDescriptionDefault
nsidNoOptional: The lexicon NSID. If provided with from_cid and to_cid, fetches schemas from storage.
to_cidNoOptional: CID of the newer version (used with nsid)
from_cidNoOptional: CID of the older version (used with nsid)
to_schemaNoOptional: The newer schema JSON (used without nsid)
from_schemaNoOptional: The older schema JSON (used without nsid)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the useful outcome traits (breaking vs non-breaking classification plus migration guidance), but says nothing about failure modes — invalid JSON, unknown NSID, unresolvable CID, or what happens if parameters from both modes are mixed.

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?

Three sentences, front-loaded with purpose, then capability, then the invocation contract. No filler and no repetition of parameter names beyond what the mode grouping requires.

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

Completeness5/5

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

For a five-parameter, zero-required comparison tool with no output schema and no annotations, the definition covers purpose, capability, and both input modes. The remaining unknowns are error behavior, which is arguably a schema/annotation concern rather than a description gap.

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 description coverage is 100%, so each parameter is already documented individually and the baseline is 3. The description does add value beyond the flat schema by pairing parameters into mutually exclusive mode groups, but with 0 required parameters it never states which combination is actually valid versus merely ignored.

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 ('Check compatibility between two versions of an ATProtocol lexicon schema') and adds scope detail by stating it detects breaking vs non-breaking changes and returns migration guidance. It doesn't explicitly differentiate itself from the sibling validate_lexicon, which is the most likely point of confusion, so it falls short of 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 Guidelines4/5

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

It gives clear operational guidance for the two invocation modes: 'Supply either two schema JSON objects directly (from_schema + to_schema), or an NSID with two CIDs to compare stored versions (nsid + from_cid + to_cid).' That is genuine mode-selection context. It does not state when to prefer this over validate_lexicon or what to do if only partial parameters are supplied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources