Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Retry recording

retry_recording
Idempotent

Restarts a failed or stalled recording edit using a recording ID and idempotency key, so processing can continue without starting over.

Instructions

Runs a recording's editing again after it failed or stalled.

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": {
      "recording_id": "<recording_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "retry_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNo
recording_idYesThe recording's id, from list_recordings.
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent, open-world mutation, so the safety profile is covered. The description adds the state requirement (must be failed or stalled), which is genuinely useful, but says nothing about whether prior edits are preserved, whether it is asynchronous (relevant given a wait_for_recording sibling), or what a caller gets back.

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?

A single front-loaded sentence with zero filler and no repetition of the title. It is tight, though its brevity is closer to under-specification than to disciplined economy.

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 two required parameters, one sentence is thin: the required idempotency_key, the account_id scoping case, and the likely asynchronous outcome all go unaddressed. The annotations carry the safety story, which keeps this from being inadequate, but the caller still has gaps to close by guessing.

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?

With only 33% schema description coverage, the description is expected to compensate and does not. It never mentions the required idempotency_key (a UUID the caller must supply) or the optional account_id scoping rule, leaving the most error-prone required parameter unexplained anywhere except its format.

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 gives a specific verb ('Runs ... editing again') and a specific resource (a recording's editing), plus the trigger state (failed or stalled). An agent can tell this is a re-run of an existing editing pipeline rather than a new upload or a re-cut, though it never explicitly distinguishes itself from siblings like recut_recording or retry_task.

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?

It states a use condition ('after it failed or stalled'), which is more than nothing, but offers no exclusions, no prerequisites, and no named alternative for the case where the user wants a fresh edit rather than a retry. The guidance is implied rather than spelled out.

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