Skip to main content
Glama

read_compare_revisions

Read-only

Compare two page revisions to see a line-by-line diff, or compare an older revision with the latest to identify changes.

Instructions

Line diff between two revisions of a page, or between one revision and the latest.

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": {
      "page": "<page>",
      "base": "<base>"
    },
    "name": "read_compare_revisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYesOlder revision id
pageYesPage id or path
targetNoNewer revision id; omit for the latest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral detail that the output is a line-level diff and that the latest revision can be used as the target, but it does not describe the diff format or any limits.

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?

The definition is a single compact sentence with the core operation front-loaded and both supported modes expressed without redundant wording. Every clause contributes directly to understanding the tool.

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

Completeness4/5

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

For a simple read-only diff tool with complete parameter documentation and safety annotations, the description covers purpose and usage modes adequately. A note on the returned diff format would make it fully complete in the absence of an output schema, but this is a minor 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 the roles of page, base, and target are already documented. The description reinforces the two-revision versus revision-to-latest modes but adds no syntax or format detail beyond what the schema provides, making the baseline score appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise operation – producing a line diff between two page revisions – and its two modes, including comparing against the latest revision. This clearly distinguishes it from sibling tools that read a single revision or list revisions.

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 by the comparison operation, but the definition gives no explicit guidance on when to choose this over read_revision or read_revisions, nor any exclusions or prerequisites. An agent can infer the use case from the purpose but is not routed explicitly.

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