Skip to main content
Glama

get_document_versions

Read-onlyIdempotent

Las versiones anteriores de un documento: copias automáticas de hace 1 minuto, 5, 10, 30 minutos, 1 y 6 horas, y 1, 2, 3 y 5 días (cada escritura, de la app o del MCP, rota las copias). Devuelve, por copia: slot, cuándo se guardó, bytes y sus primeros títulos. Para volver a una: restore_document_version.

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": {
      "document_id": "<document_id>"
    },
    "name": "get_document_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesID del documento
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: that every write from the app or the MCP rotates the copy slots, meaning version history is volatile and bounded — non-obvious and decision-relevant for an agent.

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?

Two sentences, front-loaded with the resource, then the slot list, then the return shape, then the alternative. The parenthetical about write rotation is dense but earns its place; the slot enumeration is long but functionally necessary.

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?

With no output schema, the description correctly compensates by naming the returned fields (slot, timestamp, bytes, first headings). For a simple two-parameter read tool this is close to complete; only error/empty-history behavior (e.g., what if no versions exist yet) is left unstated.

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%, so document_id and workspace_id are already documented in the schema, including the token-workspace omission rule. The description adds no parameter-level detail beyond that, which is the expected baseline here.

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 resource and verb (previous versions of a document) and immediately enumerates the retention slots (1m, 5, 10, 30m, 1/6h, 1/2/3/5d), which makes it unmistakable versus siblings like get_document or get_document_files. The closing line explicitly distinguishes it from restore_document_version.

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?

States the follow-up path clearly: 'Para volver a una: restore_document_version', which tells the agent the read-then-restore workflow. It does not spell out when to prefer this over get_document (e.g., current content vs history), so a small inference remains.

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