Skip to main content
Glama

restore_from_trash

DestructiveIdempotent

Recupera algo de la papelera (ver get_trash): vuelve a donde estaba. Un documento, canvas, recap, clip o entidad del Atlas. Una entidad restaurada levanta también el veto a ese nombre (el Atlas lo puede volver a sugerir).

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": {
      "tipo": "<tipo>",
      "id": "<id>"
    },
    "name": "restore_from_trash"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID del ítem (campo `id` de get_trash)
tipoYesQué es (el campo `tipo` de get_trash)
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the mutation/idempotent profile is covered. The description adds genuine extra behavior: the item returns to its original location, and restoring an entity also lifts the name veto so the Atlas may suggest that name again — a useful side effect. It does not address what happens if the original location no longer exists, nor why destructiveHint=true applies (e.g., overwriting an existing item), leaving the destructive flag unexplained.

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?

Front-loaded with the action and the pointer to get_trash, then the item kinds, then the side effect. Three short sentences with no filler; only the redundant restatement of item types costs it a point.

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, so the description carries the return/effect burden, and it does state the result (back to its original place) plus the Atlas-veto side effect. For a 3-param mutation with full schema coverage and annotations, only failure modes and permission expectations are missing.

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%, so the baseline is 3 and the schema already documents id, tipo and workspace_id in detail. The description only loosely echoes the tipo values and even uses a different label ('recap') than the enum value 'meeting', which adds a small ambiguity rather than new meaning.

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?

Concrete verb+resource: 'recupera algo de la papelera... vuelve a donde estaba', with an explicit cross-reference '(ver get_trash)' and an enumeration of item kinds (documento, canvas, recap, clip, entidad). It clearly separates itself from unrelated siblings, though it does not explicitly contrast with restore_document_version / restore_artifact_version, so an agent must infer that this one is the trash path.

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 parenthetical '(ver get_trash)' tells the agent where to source the id/tipo, which is real usage guidance. However there is no explicit statement of when NOT to use it (e.g., version restore vs trash restore) and no precondition such as requiring the item to still be in the trash.

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