Skip to main content
Glama

Take back a submission

remove_figures
DestructiveIdempotent

Delete a submission the person sent, with the removal code it gave them.

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": {
      "code": "<code>"
    },
    "name": "remove_figures"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe 20-character removal code

Output Schema

NameRequiredDescriptionDefault
reportVersionYesThe report's shape version (now 2.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds a genuine behavioral detail beyond them: the removal code acts as the capability that both identifies and authorizes deletion of that specific submission. It still never states that deletion is permanent and irreversible for the submitter.

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. It is efficient, though the phrase 'the person sent' is a slightly indirect way to say 'user-submitted' and costs a few words for no added precision.

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

Completeness3/5

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

With an output schema present and only one fully documented parameter, the definition covers enough to invoke the tool. For a destructive, open-world operation it should still say plainly that the submission is permanently gone and that an invalid or already-used code yields a failure, since idempotency makes repeat calls ambiguous.

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% and the 20-character format is documented there, so the schema does the heavy lifting. The description contributes the origin of the code — it is the token given to the person who submitted — which helps the agent understand why the value cannot be guessed or constructed.

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 concrete verb and object — deleting a submission — and clarifies the deletion is keyed by a removal code, which separates it from the submission-creating sibling. It never uses the word 'figures' from the tool name, so the agent must infer that 'submission' and 'figures' are the same resource.

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 and no named alternative. The only implicit signal is that the caller needs a removal code the submitter received, which hints at a prerequisite but does not route the agent among siblings such as submit_figures or community_figures.

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.