Skip to main content
Glama

compare_exact_versions

Read-onlyIdempotent

Compare one symbol across two exact package versions and show commit-pinned evidence.

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": {
      "package": "<package>",
      "from": "<from>",
      "to": "<to>",
      "symbol": "<symbol>"
    },
    "name": "compare_exact_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
symbolYes
packageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world operation, so the description need not repeat that. It adds useful context with 'commit-pinned evidence,' but does not explain what happens when a version fails to resolve, what the evidence contains, or whether results include source locations.

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 front-loaded sentence with no filler. The resource, scope, and key output characteristic appear immediately, and nothing is wasted.

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 four-parameter, read-only comparison tool with no output schema, the description is adequate but thin. It does not cover resolution failure behavior, result shape beyond 'commit-pinned evidence,' or the meaning of 'exact' when a version is missing, all of which an agent may need before calling 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 description coverage is 0%, so the description must carry meaning. It does imply the four fields (package, two exact versions, one symbol) and the constraint of a single symbol, but it does not clarify package ecosystem syntax, version-string format, or symbol notation such as export name versus file path.

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 ('Compare') and a precise scope: one symbol across two exact package versions, returning commit-pinned evidence. It does not explicitly name or distinguish itself from the sibling tools resolve_exact_version or list_coverage, so it falls just 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 Guidelines3/5

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

Usage is implied: an agent should use this when it already has two exact package versions and wants to compare a single symbol. There is no explicit when-not guidance, no mention of alternatives, and no statement about prerequisites such as both versions needing to resolve.

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