Skip to main content
Glama

restore_document_version

Destructive

Vuelve un documento a una de sus versiones anteriores (get_document_versions): REEMPLAZA el contenido actual. Lo que tenía hasta ahora queda como versión sólo si ya había pasado el tiempo de su copia; lo escrito en el último minuto puede perderse.

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

Input Schema

NameRequiredDescriptionDefault
slotYesEl slot de la versión (ej. '1m', '1h', '2d')
document_idYesID del documento
base_versionNoupdated_at con el que se leyó
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.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real value: it explains that current content survives only as a version if the snapshot interval has elapsed, so edits from the last minute may be lost. That data-loss nuance is not in the annotations or schema. It does not discuss base_version concurrency rejection, hence not a 5.

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?

Three compact sentences that front-load the destructive action, then the recovery caveat. No filler, and capitalization is used to flag the single most important fact.

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?

Complete for a destructive mutation with no output schema: the what, the how-to-find-versions path, and the recovery limitation are all covered. Only a note on what base_version does on conflict would improve it.

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 slot, document_id, base_version and workspace_id are already documented in the schema. The description adds no parameter-level syntax, defaults, or guidance (e.g. how slot values map to restore points), so it adds little beyond the structured data.

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 ("Vuelve un documento a una de sus versiones anteriores") and distinguishes the operation from browsing by pointing to get_document_versions in parentheses. Capitalized REEMPLAZA makes the mutating nature unmistakable.

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?

Makes clear this is the tool to call to revert a document, and directs the agent to get_document_versions to discover versions, which is the key prerequisite. It stops short of stating explicit exclusions (e.g. for artifacts or trashed documents) but the context is unambiguous.

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