Skip to main content
Glama

Withdraw a pending action

cancel_pending_action

Withdraw a pending action you requested. Withdrawing approves nothing.

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": {
      "pending_action_id": "<pending_action_id>"
    },
    "name": "cancel_pending_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
pending_action_idYesUUID of the pending action to withdraw

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 readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the agent knows this is a non-destructive local mutation. The description adds genuine context not in the annotations: the action must be one the caller requested, and withdrawing does not grant approval. It does not address what happens on a repeat call despite idempotentHint=false, nor what the caller gets back.

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?

Two short sentences, both front-loaded with the key information: the action first, then the crucial non-approval caveat. Nothing is padded and no sentence is wasted.

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?

For a single-parameter tool with a fully documented schema and clear annotations, the description covers the essentials. With no output schema, it leaves unstated what the call returns (e.g. the updated action or a confirmation) and how a failed or already-processed withdrawal behaves.

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 sole parameter already carries a description ('UUID of the pending action to withdraw'). The description adds only the ownership constraint implied by 'you requested'; with the schema doing the heavy lifting, the baseline 3 is appropriate.

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 states a specific verb and resource ('Withdraw a pending action') and scopes it with 'you requested', which separates it from the read-oriented siblings get_pending_action and list_pending_actions. It stops short of naming an alternative explicitly, so a 4 rather than a 5.

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?

'you requested' implies the ownership precondition for when this applies, and 'Withdrawing approves nothing' implicitly warns against using it to approve. There is no explicit when-to-use/when-not guidance or named alternative for approving or querying a pending action.

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