Skip to main content
Glama

retry_feature

Resets a failed feature to pending status so it can be retried after issues are fixed or auto-retry attempts are exhausted.

Instructions

Reset a failed feature to pending status so it can be retried. Use this to manually retry a feature after fixing issues or when auto-retry has been exhausted.

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": {
      "projectDir": "<projectDir>",
      "featureId": "<featureId>"
    },
    "name": "retry_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
featureIdYesID of the feature to retry
projectDirYesAbsolute path to the project directory
resetAttemptsNoWhether to reset the attempt counter to 0 (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose the key behavior: a failed feature is moved to pending, and this is the manual counterpart to auto-retry. It omits important traits such as what happens if the feature is not in a failed state, whether resetting triggers immediate re-execution, and whether the operation is idempotent or reversible.

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, no filler, and the core state transition is front-loaded before the usage note. Every clause contributes information an agent needs.

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 three-parameter mutation tool with no annotations and no output schema, the definition covers purpose, preconditions, and trigger conditions adequately. It leaves gaps around return values (nothing reports success or the new state) and around behavior when preconditions are not met, which an agent must guess at.

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 description coverage is 100%, so all three parameters, including resetAttempts with its default, are already documented in the schema. The description adds no parameter-level detail such as the effect of resetting attempts on retry limits. Baseline 3 applies when the schema does the heavy lifting.

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 concrete verb and resource with the resulting state change: 'Reset a failed feature to pending status so it can be retried.' That is far more specific than a tautology and clearly signals a state-machine mutation on a feature. It stops short of 5 because it doesn't position itself against adjacent siblings like rollback_feature or enqueue_feature.

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

Usage Guidelines4/5

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

It gives explicit triggering conditions: after fixing issues, or when auto-retry has been exhausted. That is genuine when-to-use guidance rather than implied usage. There are no exclusions (e.g., what to do if the feature is not failed) and no named alternative tool, which keeps it below 5.

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