Skip to main content
Glama
cryptograss

MediaWiki MCP Server

by cryptograss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-revision

Read-onlyIdempotent

Retrieve a specific historical wiki page revision by ID, returning wikitext, HTML, or metadata. Errors if the revision ID does not exist.

Instructions

Returns a specific historical revision of a wiki page by revision ID (wikitext source, rendered HTML, or metadata only). If the revision ID does not exist, an error is returned. Content is truncated at 75000 bytes by default; a past revision has no narrower read, so for a large one use compare-pages to see what changed. For the latest revision plus metadata, use get-page with metadata=true.

Input Schema

NameRequiredDescriptionDefault
wikiNoWiki to target, as a key from the mcp://wikis/ resources (e.g. en.wikipedia.org), or the full mcp://wikis/ URI. Omit to use the default wiki.
contentNoType of content to returnsource
metadataNoWhether to include metadata (revision ID, page ID, page title, user ID, user name, timestamp, comment, size, minor, HTML URL) in the response
revisionIdYesRevision ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.19.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable behavioral context: content truncation at 75000 bytes, error on missing revision, and the note that a past revision has no narrower read. These details go beyond annotations and set correct expectations.

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?

Three sentences with no redundancy. The purpose is front-loaded, followed by error and truncation details, then alternative tools. Every sentence adds value and the structure is easy to scan.

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

Completeness5/5

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

For a read-only revision retrieval tool with high schema coverage and no output schema, the description covers purpose, error cases, truncation, and alternatives. Nothing essential is missing for an agent to call it 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 coverage is 100% and every parameter has a description. The tool description does not add per-parameter semantics beyond what the schema provides; it only restates content types and metadata in prose. Since schema carries the burden, baseline 3 is 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 specific verb and resource: returns a specific historical revision by revision ID, with content types (source, HTML, or metadata). It distinguishes from get-page (latest revision) and compare-pages (diff). The purpose is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly guides when to use alternatives: 'For the latest revision plus metadata, use get-page with metadata=true' and 'for a large one use compare-pages to see what changed.' Also notes error behavior on non-existent revision. Clear routing.

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

Deploy Server

Other Tools