Skip to main content
Glama

document_delete

Delete ONE language version of a document.

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

Input Schema

NameRequiredDescriptionDefault
document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether the deletion is irreversible, what happens to the remaining language versions, whether the last version's removal deletes the document, or what permissions are needed. "Delete" implies a destructive mutation but the description never confirms or characterizes it.

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?

A single front-loaded sentence with no filler, and the capitalized "ONE" usefully emphasizes the narrow scope. It is efficient but so terse that brevity shades into under-specification for a destructive operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with no annotations and no output schema, the description should explain irreversibility, scope, and how the language version is identified. None of that is present, and the missing language selector is a real gap an agent would hit at call time.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter document_id is never mentioned. More importantly, the description says one language version is deleted yet the schema exposes no language identifier, so the description leaves genuine ambiguity about how the target version is chosen.

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 gives a specific verb and resource ("Delete ... a document") and adds a meaningful scope qualifier, "ONE language version", which tells the agent this does not remove the whole document. It stops short of distinguishing itself from siblings such as document_update or document_add_languages beyond that phrase.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, no mention of how to remove an entire document instead of one language version, and no prerequisites such as required roles or confirmation. The "ONE language version" wording hints at narrow scope but never states the conditions that select this tool.

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