Skip to main content
Glama

Read the recent history of a tool document

tools_get_history
Read-only

Return the most recent events on a document, newest first, each with its event id and a plain description. Use an event id with a RestoreTo command to put the document back to the state right after that event.

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": {
      "documentId": "<documentId>"
    },
    "name": "tools_get_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many entries (default 20, max 100).
documentIdYesThe document id, from tools_list_documents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds behavioral detail the annotations do not: results are ordered newest first, each entry carries an event id and a plain description, and event ids are the input a RestoreTo command expects. What it does not say is how much history is kept or how the result is paginated beyond the limit.

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?

Two sentences, no filler, and the return shape and ordering are front-loaded before the downstream use of event ids. Every clause carries information an agent needs.

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?

There is no output schema, so the description has to explain the return values itself, and it does: newest-first ordering and the contents of each entry. Because the parameters are fully documented in the schema, the only real gap is retention depth or pagination behavior.

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 100% and both parameters are documented there, including the limit default of 20 and maximum of 100. The description adds nothing about either parameter, so the schema is doing all the work and 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?

The description names a specific verb ("Return") and resource ("the most recent events on a document"), plus the ordering and the shape of each entry. That is enough to separate it from tools_get_document, which returns the document itself, but it never names a sibling or an alternative 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?

The second sentence implies the primary workflow: an event id from this tool feeds a RestoreTo command. That is usage context, not selection guidance, and there is no explicit statement of when to call this versus tools_get_document or when not to call it.

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