Skip to main content
Glama

Page history

wiki_history
Read-only

How a page or a table row got to be as it is, newest first: a page's revisions, or with key a row's versions.

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": {
      "path": "<path>",
      "org": "<org>"
    },
    "name": "wiki_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoA row of the table, by key; without it, the page's revisions.
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe wiki's name, a colon, then the page's dot-separated path (general:docs.deploy).
limitNo
cursorNoWith key, continue the previous read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds one genuine behavioral fact beyond the annotations: results are ordered 'newest first'. It says nothing about pagination behavior, volume of results, or what a revision record contains.

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 compact sentence with the ordering and the page-vs-row distinction front-loaded and no filler. The phrasing is slightly convoluted ('got to be as it is') 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 five-parameter read tool with no output schema, the definition covers the mode split and ordering but leaves pagination semantics and the shape of returned revisions unexplained. It is adequate to invoke correctly, but not complete for interpreting results.

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 80%, so the schema already documents key, org, path, and cursor. The description reinforces the key/no-key distinction but adds no format, constraint, or interaction detail (e.g. how limit interacts with cursor) beyond what the schema states.

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 the resource and its meaning concretely ('a page's revisions, or with key a row's versions'), which distinguishes the two modes of the tool. The verb is expressed indirectly ('How a page ... got to be as it is') rather than as a crisp 'list revisions', but an agent can still tell this is a history/versions read.

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 only implied: it tells you to supply 'key' when you want row versions instead of page revisions, which is a useful branch condition. There is no explicit statement of when to prefer this over siblings like wiki_changes or wiki_get, and no exclusions or prerequisites beyond the schema-required org/path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources