Skip to main content
Glama

Show karaoke

show_karaoke
Read-only

Display only the finished karaoke MP4 preview and download. First call get_karaoke and verify ready/handed_off, project.has_export=true, project.export_status=ready and no lyrics review. Never use this for upload, a price quote, confirmation, processing or errors: handle those in the conversation. Omit visual_preferences; the legacy optional field cannot change a saved design. Does not start processing.

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>"
    },
    "name": "show_karaoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
visual_preferencesNo

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
presentation_visual_preferencesNo

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

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real context beyond them: preconditions on project state, the fact that it does not start processing, and that the legacy visual_preferences field cannot alter a saved design. It stops short of describing what the rendered preview contains or how the download is delivered, so it is strong but not exhaustive.

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?

Front-loads the core action in one sentence, then preconditions, then exclusions, then the parameter caveat — every clause carries operational information with no filler. The state field paths are terse but precise rather than verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 no explanation, and the description covers preconditions, exclusions and the one misleading optional parameter, which is what an agent needs to invoke it correctly. The only residual gap is that nothing describes what the preview surface or download actually returns beyond the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameter burden; it does explain that visual_preferences should be omitted because the legacy optional field cannot change a saved design, which is meaning not present in the schema. project_id is only implicitly covered through the state-verification preconditions rather than described directly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (display the finished karaoke MP4 preview and download) and immediately carves out scope by naming what it is not for (upload, price quote, confirmation, processing, errors). An agent can distinguish it from siblings like get_karaoke, prepare_karaoke and start_karaoke without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit precondition sequence: call get_karaoke first and verify ready/handed_off, project.has_export=true, project.export_status=ready, and no lyrics review. It also lists explicit when-not cases (upload, quote, confirmation, processing, errors) with the instruction to handle those in conversation, which is a full routing rule.

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