Skip to main content
Glama

Patch MCP

resume_operation

Destructive

Recover an interrupted number claim or subscription attempt owned by this account and the original authorization grant. Requires that operation's original permissions. May reconcile number provisioning or retry the persisted subscription request with its original idempotency key. Never creates a replacement request or authorizes new spending. Completed results and definitive failures are returned without repeating provider actions.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "resume_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, openWorldHint=true, idempotentHint=false), the description discloses the actual mutation surface: it may reconcile number provisioning or retry the persisted subscription request using the original idempotency key, and it will not authorize new spending or create a replacement request. It also tells the agent that already-completed and definitively-failed operations return without re-contacting the provider, which meaningfully shapes retry behavior. It does not elaborate on what a destructive reconcile could alter, but the key side effects are named.

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?

The scope and the primary constraint ("Recover an interrupted...") are front-loaded, then permissions, then side effects, then non-actions. Sentences are dense but each adds a distinct fact; the closing sentence on completed/definitive-failure results is valuable rather than filler. Slightly long, but no sentence is redundant.

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?

With an output schema present, the description is not obliged to document return values, and it still sketches the key outcome classes (recovered, already completed, definitively failed). For a destructive, open-world, single-parameter recovery tool the remaining gap is how an agent discovers a recoverable operation_id, which is left to get_operation.

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?

There is a single parameter (operation_id) and the schema has 0% description coverage, so the description carries the burden of explaining it. It conveys that the identifier belongs to an interrupted operation owned by this account and tied to the original authorization grant, which adds real meaning, but it never explains the accepted format, where the value comes from, or the minimum/200-character constraints. Adequate, not complete.

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?

"Recover an interrupted number claim or subscription attempt" gives a specific verb (recover) and a precisely scoped resource (an already-started claim/subscription owned by this account). It implicitly separates itself from creation tools by stating it never creates a replacement request, so an agent can tell it is not claim_phone_number or execute_subscription_change. It stops short of naming those siblings explicitly.

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 intended context is clear from "interrupted ... attempt" and "Requires that operation's original permissions," which is a real precondition. However, it never states the trigger conditions operationally (e.g., after a failed or timed-out claim) nor points at get_operation for obtaining the operation_id or for checking whether recovery is needed. Usage is implied rather than instructed.

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