Skip to main content
Glama

withdraw_entry

DestructiveIdempotent

Withdraw your own report, topic, or reply from public results.

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": {
      "entry_id": "<entry_id>"
    },
    "name": "withdraw_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes

Output Schema

NameRequiredDescriptionDefault
entryYes

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 destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds a meaningful nuance with "from public results," hinting that the entry is removed from public view rather than necessarily erased, but it never states permanence, recoverability, or whether the underlying content survives.

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 ownership and visibility constraints appear immediately. It is perhaps overly terse for a destructive operation, but every word earns its place.

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?

The output schema and annotations carry the return-shape and safety burden, and the description covers the core action and scope. The remaining gap is behavioral: for a destructive, irreversible-sounding action it should say whether withdrawal is reversible and what happens to the underlying entry.

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 0%—entry_id is documented only as a pattern-constrained string. The description partially compensates by indicating that the identifier may point to a report, topic, or reply, which tells the caller the accepted entry types, but it adds nothing about the ID format or how to obtain one.

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 names a specific verb ("Withdraw") plus the exact resources affected (report, topic, or reply) and the scope ("your own", "from public results"). It is unambiguous against siblings such as create_topic or reply_to_topic, though it does not explicitly contrast itself with any alternative removal 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 phrase "your own" implies an ownership precondition, which is useful usage guidance, but there is no explicit when-to-use/when-not-to-use statement, no mention of required confirmation, and no named alternative for cases where the entry should be hard-deleted rather than withdrawn.

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