Skip to main content
Glama

operation_retry

DestructiveIdempotent

Resume failed or interrupted non-submission work by creating a separate retry attempt while preserving the original failure record.

Instructions

Resume failed/interrupted non-submission work. Creates a separate attempt and preserves the original failure.

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>",
      "op_id": "<op_id>"
    },
    "name": "operation_retry"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
operation_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 readOnlyHint=false. The description adds real value by explaining that a separate attempt is created and the original failure is preserved, which is the key side-effect an agent needs. It never says what the destructive aspect actually destroys or whether permissions are required, so it leaves a gap against destructiveHint=true.

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?

Two short sentences, front-loaded with the action and immediately followed by the side-effect, with no filler. The terseness is appropriate, though the space saved could have been spent on the two undocumented IDs.

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

Completeness2/5

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

An output schema exists, so return values need no explanation, but for a destructive, retry-style mutation the description is thin: no state eligibility rules, no mention of the two required ID parameters, and no note on what the destructive flag implies. What is present is correct but insufficient for how consequential the tool is.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (op_id and operation_id) are required with 0% schema description coverage, and the description does not mention either one. It gives no clue how op_id differs from operation_id, which is exactly the ambiguity the description should resolve when the schema is silent.

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?

"Resume failed/interrupted ... work" gives a specific verb and resource, and "non-submission" scopes it away from the submit-family siblings (analysis_submit, batch_submit). The phrase "non-submission work" is somewhat opaque but the core action is unmistakable.

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?

It implies a context (failed or interrupted operations) but names no alternative and gives no prerequisites, such as which operation states qualify or what to do if the original work was a submission. The agent must infer when retry is preferable to operation_get plus a fresh call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.