Skip to main content
Glama

List Document History

list_document_revisions
Read-onlyIdempotent

List the saved versions of a document you own, newest first: the revision (such as "r12"), who changed it, what they did, the size change, and when. No document text. Use it before restore_document_revision, or to see what changed since you last looked. Older versions are removed over time according to your plan. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe slug of the document
limitNoHow many versions to return (1 to 50). Default 20.
beforeNoPass the "next" revision from the previous page to see older versions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint, but the description adds context annotations cannot carry: results are newest-first, entries exclude document text, and 'Older versions are removed over time according to your plan' warns that history is not guaranteed complete. Minor gaps remain (no statement on what a paginated empty page means), but this is well beyond the annotation baseline.

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?

Front-loaded with verb and resource, then the field list, then usage, then the read-only affirmation. The short 'No document text.' fragment earns its place by pre-empting the most likely wrong expectation, and no sentence is redundant.

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?

No output schema exists, and the description compensates by describing the return fields and ordering. Combined with retention and pre-restore guidance, an agent has enough to call it correctly and interpret results; only edge-case behavior (empty history, expired cursors) is unaddressed.

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 each of the three parameters is documented inline, so the baseline is 3. The description's 'newest first' and retention note give useful framing for `limit` and `before`, but it does not explain the `before` cursor mechanics ('Pass the "next" revision from the previous page') that the schema itself supplies.

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?

States a specific verb and resource ('List the saved versions of a document') plus ordering ('newest first') and enumerates exactly what each entry contains: revision id, author, action, size delta, timestamp. The explicit 'No document text' clause separates it from get_document/append_to_document style siblings without needing their schemas.

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

Usage Guidelines4/5

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

Gives concrete usage contexts: 'Use it before `restore_document_revision`, or to see what changed since you last looked.' The pre-restore sequencing against a named sibling is genuinely actionable. It stops short of an explicit when-not statement (e.g. 'do not use to read content, use get_document'), so it is clear context rather than full routing.

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.