Skip to main content
Glama

Retry karaoke

retry_karaoke

Retry a failed or stale Quick stage only when can_retry is true. Keeps the existing project, saved visual preferences and completed stages. This does not request a new creative design.

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": {
      "project_id": "<project_id>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "retry_karaoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
idempotency_keyYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault
errorNo
mediaNo
quoteNo
stageNo
statusNo
visualNo
projectNo
progressNo
can_retryNo
can_startNo
demo_modeNo
can_cancelNo
project_idNo
studio_urlNo
can_handoffNo
lyrics_sourceNo
preview_readyNo
visual_sourceNo
visual_warningNo
command_versionNo
project_revisionNo
can_replace_lyricsNo
can_update_visualsNo
visual_preferencesNo
needs_lyrics_reviewNo
lyrics_search_outcomeNo
lyrics_search_providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / oneOf
      Previous value: -[
      -  {
      -    "required": [
      -      "project_id",
      -      "project_revision",
      -      "command_version",
      -      "status",
      -      "stage",
      -      "quote",
      -      "can_start",
      -      "can_retry",
      -      "can_cancel",
      -      "can_handoff",
      -      "preview_ready",
      -      "needs_lyrics_review",
      -      "progress",
      -      "visual_preferences",
      -      "visual",
      -      "visual_source",
      -      "visual_warning",
      -      "error",
      -      "lyrics_source",
      -      "lyrics_search_outcome",
      -      "lyrics_search_provider",
      -      "demo_mode",
      -      "project",
      -      "studio_url",
      -      "media"
      -    ]
      -  },
      -  {
      -    "maxProperties": 1,
      -    "properties": {
      -      "error": {
      -        "additionalProperties": true,
      -        "maxProperties": 32,
      -        "properties": {
      -          "code": {
      -            "maxLength": 120,
      -            "minLength": 1,
      -            "type": "string"
      -          },
      -          "message": {
      -            "maxLength": 2000,
      -            "minLength": 1,
      -            "type": "string"
      -          },
      -          "retryable": {
      -            "type": "boolean"
      -          }
      -        },
      -        "required": [
      -          "code",
      -          "message",
      -          "retryable"
      -        ],
      -        "type": "object"
      -      }
      -    },
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "required": [
      +      "project_id",
      +      "project_revision",
      +      "command_version",
      +      "status",
      +      "stage",
      +      "quote",
      +      "can_start",
      +      "can_retry",
      +      "can_cancel",
      +      "can_handoff",
      +      "preview_ready",
      +      "needs_lyrics_review",
      +      "can_replace_lyrics",
      +      "can_update_visuals",
      +      "progress",
      +      "visual_preferences",
      +      "visual",
      +      "visual_source",
      +      "visual_warning",
      +      "error",
      +      "lyrics_source",
      +      "lyrics_search_outcome",
      +      "lyrics_search_provider",
      +      "demo_mode",
      +      "project",
      +      "studio_url",
      +      "media"
      +    ]
      +  },
      +  {
      +    "maxProperties": 1,
      +    "properties": {
      +      "error": {
      +        "additionalProperties": true,
      +        "maxProperties": 32,
      +        "properties": {
      +          "code": {
      +            "maxLength": 120,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "message": {
      +            "maxLength": 2000,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "retryable": {
      +            "type": "boolean"
      +          }
      +        },
      +        "required": [
      +          "code",
      +          "message",
      +          "retryable"
      +        ],
      +        "type": "object"
      +      }
      +    },
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / can_replace_lyrics
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / can_update_visuals
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / project / properties / has_lyrics
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / project / required
      Previous value: -[
      -  "id",
      -  "title",
      -  "artist",
      -  "duration_seconds",
      -  "revision",
      -  "has_export",
      -  "export_status",
      -  "visual_settings"
      -]New value: +[
      +  "id",
      +  "title",
      +  "artist",
      +  "duration_seconds",
      +  "revision",
      +  "has_export",
      +  "has_lyrics",
      +  "export_status",
      +  "visual_settings"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, non-open-world write, and the description adds genuinely non-obvious behavior: the existing project, saved visual preferences and completed stages are preserved, and no new creative design is generated. It does not address cost/quota implications (notable given a sibling quote tool exists) or what happens to the stale stage's prior output, so it is strong but not complete.

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?

Three short sentences, with the gating condition front-loaded before the retention guarantees and the negative scope statement. No filler and nothing repeated from the title.

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?

An output schema exists, so return values need not be explained, and annotations plus the retention sentence cover much of the behavior. But for a three-parameter mutation with zero schema descriptions, the complete absence of parameter guidance leaves a real hole an agent must guess around.

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?

Schema description coverage is 0%, so the description must carry the burden, yet it never mentions project_id, expected_revision, or idempotency_key. The concurrency-control semantics of expected_revision and the deduplication contract of idempotency_key — both non-obvious and both required — are entirely undocumented anywhere the agent can see.

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 and object ("Retry a failed or stale Quick stage") and explicitly rules out the adjacent creative action ("does not request a new creative design"), which separates it from prepare/start style siblings. The only softness is the internal term "Quick stage," which is not defined for a reader unfamiliar with the product vocabulary.

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 states a clear precondition — retry is appropriate only for a failed or stale stage and only when can_retry is true — which is a real gating rule an agent would otherwise get wrong. It stops short of naming a concrete alternative to call when can_retry is false (e.g., re-prepare or start), so the negative branch is left implicit.

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.

Resources