Skip to main content
Glama

read_revision

Read-only

Retrieve the full content of a specific past page revision using a page identifier and revision ID, so you can inspect or compare historical versions.

Instructions

One past revision of a page with its full content.

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>",
      "revision": "<revision>"
    },
    "name": "read_revision"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
revisionYesRevision id from read_revisions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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 safety and locality are covered. The description adds the one behavior that matters beyond that: the response includes full content, not just revision metadata. It does not state the content format or what happens with an invalid revision id, so it adds some but not rich context.

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?

A single short sentence with zero filler, front-loading the object and the returned payload. It is slightly under-specified rather than verbose, but 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 two-parameter read tool with no output schema and read-only annotations, the description covers what the tool returns at a high level. It omits the content format (raw/wikitext/rendered) and error behavior for missing revisions, leaving minor gaps an agent might care about.

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%: both 'page' (id or path) and 'revision' (id from read_revisions) are documented in the schema. The description adds no further meaning beyond what the schema already provides, so the baseline 3 applies.

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 phrase 'one past revision of a page with its full content' names the resource (a single historical revision) and adds the key differentiator, full content, which implies it is not just a metadata listing. The verb is implicit rather than stated, but the noun phrase is specific enough that an agent can distinguish it from the plural read_revisions sibling.

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 explicit when-to-use guidance and no alternative named. The agent must infer that this tool should follow read_revisions (the schema mentions 'Revision id from read_revisions', but that routing hint lives in the parameter description, not the tool description). No exclusions or prerequisites are stated.

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