Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Retry task

retry_task
Idempotent

Request a safe task retry with goal ID, task ID, expected version, and reason; budget, authority, and uncertain paid calls are checked first.

Instructions

Requests a safe retry of a task, using its current goal id, task id and version. The backend reconciles uncertain paid calls and sends and checks current budget and authority first. Conference tasks may need more detail.

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": {
      "goal_id": "<goal_id>",
      "task_id": "<task_id>",
      "expected_version": "<expected_version>",
      "idempotency_key": "<idempotency_key>",
      "reason": "<reason>"
    },
    "name": "retry_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
goal_idYes
task_idYes
idempotency_keyYes
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the backend reconciles uncertain paid calls and sends and checks budget and authority first — meaningful side-effect and precondition context an agent would not otherwise know. It stops short of describing what happens on version mismatch or budget failure, so it is not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are tight and front-loaded, but the trailing "Conference tasks may need more detail" is vague filler that gives the agent nothing actionable. Overall it is compact and readable, just not uniformly purposeful.

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 mutation tool with no output schema and zero schema-level parameter documentation, the description should do more: it omits the meaning of two required parameters and any indication of what a successful retry returns or how failures surface. The core behavioral contract is present but incomplete.

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 0% across five required parameters, so the description carries the burden. It explains goal_id, task_id and expected_version as the task's current identity, but says nothing about idempotency_key or the reason field, leaving two required parameters with no semantic guidance anywhere.

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?

States a specific verb and resource ("Requests a safe retry of a task") and names the identifying inputs (goal id, task id, version). It is clear what the tool does, though it never contrasts itself with likely siblings such as resume_task or retry_recording, so an agent must infer the boundary.

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 phrase "safe retry" and the note that "Conference tasks may need more detail" imply context, but there is no explicit when-to-use / when-not-to-use guidance and no named alternative for a plain resume versus a retry. Usage is only implied rather than directed.

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

Deploy Server

Other Tools