Skip to main content
Glama

write_restore_revision

Restore a LeafWiki page to a selected past revision while preserving the current version in the page history.

Instructions

Bring a page back to a past revision (the current state stays in the history).

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": "write_restore_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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, but the description adds genuinely useful context beyond them: the current state is preserved in history, so the restore is recoverable rather than a permanent overwrite. It stops short of stating permission requirements or what the returned result looks like, but that is a minor gap given the annotations.

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 parenthetical about history is the one extra clause and it earns its place by clarifying reversibility.

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 two-parameter mutation tool with a fully described schema and annotations covering the safety profile, the description conveys what is needed to call it correctly. The only omission is the result of the operation, which is modest with no output schema present.

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 coverage is 100%, with both parameters self-documented, including 'Revision id from read_revisions.' The description adds no meaning beyond the schema, 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?

States a specific verb-and-resource pair: bringing a page back to a past revision. It is clearly distinct from read-only siblings like read_revision or read_compare_revisions by the verb 'bring back,' though it does not name any sibling explicitly.

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 phrase 'a past revision,' and the schema points to read_revisions as the source of the revision id. However, the description itself gives no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as read_compare_revisions for previewing changes.

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