Skip to main content
Glama

Retry execution

retry_execution
Destructive

Retry a terminal execution (failed, cancelled, or timeout): a new execution is created with the original's payload and runs from the start. Read the failure first with get_execution_details - retrying without fixing the cause reproduces it.

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": {
      "execution_id": "<execution_id>"
    },
    "name": "retry_execution"
  }
}

Input Schema

NameRequiredDescriptionDefault
execution_idYesExecution id (UUID) from list_recent_executions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true, but the description explains why: a brand-new execution is created and re-runs from the beginning, so work is duplicated rather than resumed. It does not cover permissions or what happens to the original execution, keeping it just short of a 5.

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 sentences, zero padding. The core behavior is front-loaded and the caution follows immediately, with no restating of the title or schema.

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?

For a single-parameter mutation with no output schema, the description covers eligibility, mechanics and the prerequisite check. It could note whether the new execution's id is returned for tracking, but nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100% and the id's origin (list_recent_executions) is documented in the schema, so baseline is 3. The description adds real meaning: only terminal executions (failed, cancelled, timeout) are valid targets, and no payload need be supplied because it is copied from the original.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (retry) and resource (execution), plus the exact eligible states (failed, cancelled, timeout) and the mechanic: a new execution with the original's payload runs from the start. This is clearly distinguishable from siblings like get_execution_details or cancel_execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the prerequisite step and the sibling to use first: read the failure with get_execution_details, and warns that retrying without fixing the cause reproduces it. That gives both when-to-use and a caution against misuse.

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.