Skip to main content
Glama

Cancel karaoke

cancel_karaoke
Destructive

Cancel this Quick workflow when can_cancel is true. Stops successor stages; completed preparation charges follow the existing service rules.

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": "cancel_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

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description earns credit for going further: it discloses that successor stages are stopped and that completed preparation charges still apply. 'Follow the existing service rules' is vague about actual billing consequences, keeping it 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.

Conciseness4/5

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

Two tight sentences, front-loaded with the core action and precondition before the side-effect details. Dense domain jargon ('Quick workflow', 'successor stages') costs a little clarity but no sentence is padding.

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 destructive mutation the description covers downstream effects and charge behavior, and an output schema exists so return values need no explanation. The gap is the complete silence on the three required arguments and on what happens if expected_revision is stale, which is material for a concurrency-guarded cancel.

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% and the description explains none of the three required parameters — no mention of project_id, expected_revision (an optimistic-concurrency guard whose failure mode matters here), or idempotency_key. It instead introduces 'can_cancel', which is not an input parameter, so the reader gets no mapping between prose and arguments.

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 ('Cancel this Quick workflow'), which clearly separates it from siblings like start_karaoke, retry_karaoke, and prepare_karaoke. The only dilution is the loose term 'Quick workflow', which is not the same vocabulary as the tool name's 'karaoke', leaving a small naming mismatch an agent must bridge.

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?

Gives a concrete gating precondition ('when can_cancel is true'), which is genuine when-to-use guidance. However it never says where can_cancel comes from (presumably a read such as get_karaoke) and does not contrast this with retry_karaoke or other recovery paths, so the agent must infer the lookup step.

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