Skip to main content
Glama

delete_document

DestructiveIdempotent

Manda un documento a la papelera, como el botón de la app: se recupera con restore_from_trash (get_trash lo lista).

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": "delete_document"
  }
}

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.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds the non-obvious behavioral fact that the effect is reversible through restore_from_trash. That resolves the apparent tension between a 'destructive' hint and recoverability, which is exactly the extra context an agent needs before mutating data.

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?

A single sentence that front-loads the action and its trash semantics, then appends the recovery/listing pointers in parentheses. No redundant wording and nothing to trim.

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?

For a two-parameter, fully documented tool with no output schema, the description covers the essentials: what it does, that it is reversible, and which tools to use next. It stops short of stating behavior for edge cases (e.g., a document already in the trash) or what the call returns, which is a minor gap given the idempotent hint.

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 the schema already explains both document_id and the workspace_id fallback semantics, so the description need not repeat them. It adds no parameter-level meaning beyond the schema, which is acceptable at the baseline.

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 ("Manda un documento a la papelera") and immediately qualifies the operation as a soft delete via the app-button analogy, so an agent knows this is not a permanent purge. It also names the sibling tools involved in the lifecycle (restore_from_trash, get_trash), distinguishing it from the many other delete_* siblings.

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 clear usage context (trash-style removal) and routes the agent to restore_from_trash for recovery and get_trash for listing, which is the key when-to-use information. It does not explicitly exclude or contrast with adjacent siblings such as delete_document_file, but the guidance that matters for correct invocation is present.

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