get_deletion_requestCheck the status of a submitted deletion request using its request_id, helping AI agents track human-reviewed quarantine progress without delete access.
Show the current status of one of your deletion requests.
| Name | Required | Description | Default |
|---|---|---|---|
| request_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds only the ownership scoping ('your'), and says nothing about behavior when a request is still pending, completed, or the ID is unknown.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with no filler, and the verb plus resource are front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read tool with no output schema, the agent still doesn't know what 'status' contains (states, fields, terminal vs in-progress values) or how to interpret a pending request, which is exactly what the tool exists to reveal.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
One required parameter with 0% schema description coverage, so the description must carry the burden. 'One of your deletion requests' hints at the ID's origin and ownership, but no format, source tool, or error behavior is given for request_id.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb ('Show') and resource ('the current status of one of your deletion requests'), which an agent can distinguish from the sibling tools that create or list requests. It never names those siblings explicitly, so differentiation relies on inference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'one of your deletion requests' implies a request_id obtained from request_deletion or list_my_deletion_requests, but the description gives no explicit when-to-use, no deadline/retention context, and no mention of alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.