Skip to main content
Glama

read_revisions

Read-only

Retrieve a page's revision history in reverse chronological order to review changes and trace edits. Provide a page ID or path and optional limit; revisions must be enabled.

Instructions

A page's revision history, newest first (needs revisions on).

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

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
limitNoDefault 20
cursorNonext from the previous answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds two pieces of real behavioral context beyond that: results are ordered newest first, and the call depends on revisions being enabled on the page. It says nothing about behavior when revisions are off (empty list vs. error), which would have raised the score.

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 short sentence front-loads the resource and tacks the ordering and prerequisite onto it. Nothing could be removed without losing information.

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, three-parameter tool with no output schema and full schema coverage, the definition plus schema gives an agent enough to invoke it correctly. It falls short only of describing the shape of a revision entry or the failure mode when revisions are disabled.

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% — page, limit (default 20, max 100), and cursor are fully documented in the schema. The description contributes no additional parameter semantics, so the baseline of 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 description names a specific resource (a page's revision history) and adds the ordering (newest first), so an agent knows exactly what it returns. It does not distinguish itself from the sibling read_revision (singular), which likely serves a different granularity, leaving a small ambiguity.

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 resource — call it to browse a page's history — and the parenthetical adds a prerequisite (revisions must be enabled). There is no explicit guidance on when to use read_revision, read_compare_revisions, or read_page instead, so the agent must infer the boundary.

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