Skip to main content
Glama
Sign In

Umtri

by io.umtri
OverviewDiscussionsAdmin

List the revision history of a wiki page

list_wiki_revisions

Returns what this page said before, newest first — rev number, who wrote it, when, and the body length. Bodies are not included (a history of twenty full documents is expensive to skim); read one with get_wiki rev=. Use it to answer "what did this say last week", to see whether a write of yours dropped something, and to find the rev to hand back to write_wiki mode="restore". Consecutive writes by the same actor within 30 minutes fold into one revision rather than piling up, so the list stays readable — a working session is one entry, not eight. The practical guarantee: whatever an agent does to a page in one session, the body from before that session is still a separate revision. Revisions start at the moment the ground gained this feature; edits older than that were never recorded and cannot be recovered.

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": {
      "slug": "<slug>",
      "ref": "<ref>"
    },
    "name": "list_wiki_revisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesPage slug or id.
slugYesGround slug.
limitNo
orderNoBy revision number. Default "desc" (newest first).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so unusually well: it discloses that bodies are omitted and why, that ordering is newest first, that writes by the same actor within 30 minutes collapse into one revision, and that revisions only exist from the feature's introduction so older edits are unrecoverable. Remaining gaps are the default page size for limit and any permission or error behavior for an unknown slug.

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?

Information is front-loaded: return shape first, then exclusion and alternative, then use cases, then behavioral caveats. It is dense and mostly earns its length, though the "practical guarantee" sentence restates the 30-minute folding rule in softer terms rather than adding new information.

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?

There is no output schema, so the description must convey the return shape, and it does explicitly (rev number, author, time, body length, bodies excluded). Combined with the truncation/retention caveats, an agent has everything needed to call this correctly and interpret the result without surprises.

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 75% and the schema already documents slug, ref, and the order enum, so the baseline applies. The description reinforces ordering semantics ("newest first") and explains what a rev number is used for, but says nothing about limit — its default or maximum — leaving the one undocumented parameter untouched.

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?

Names a specific verb and resource — returns the revision history of a wiki page — and immediately enumerates what each entry carries (rev number, author, timestamp, body length). It is clearly distinguished from the two siblings that touch the same data: get_wiki for reading one revision and write_wiki mode="restore" for consuming a rev number returned here.

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?

Gives explicit use cases ("what did this say last week", auditing whether your own write dropped content) and an explicit exclusion with the alternative named: bodies are not included, so read a single revision with get_wiki rev=<n>. The downstream routing to write_wiki mode="restore" tells the agent exactly where the returned rev number goes next.

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

All Umtri toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources