karaoke-maker-3000

Start karaoke

start_karaoke

Destructive

Start the quoted Quick karaoke only after the user explicitly confirms its current price and visual preferences in the conversation. Reserves the existing account balance and launches background processing. Use the current quote and revision; reuse the same key after a lost response. After starting, continue monitoring this same project with get_karaoke in the current turn until a current ready MP4, failure, cancellation or required lyrics correction. Do not finish with only a launch receipt or ask the user to request another status check. Report meaningful progress in chat; open show_karaoke only when the current MP4 is ready.

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

Input Schema

Name	Required	Description	Default
`quote_id`	Yes
`project_id`	Yes
`idempotency_key`	Yes
`expected_revision`	Yes
`visual_preferences`	No

Output Schema

Name	Required	Description	Default
`error`	No
`media`	No
`quote`	No
`stage`	No
`status`	No
`visual`	No
`project`	No
`progress`	No
`can_retry`	No
`can_start`	No
`demo_mode`	No
`can_cancel`	No
`project_id`	No
`studio_url`	No
`can_handoff`	No
`lyrics_source`	No
`preview_ready`	No
`visual_source`	No
`visual_warning`	No
`command_version`	No
`project_revision`	No
`can_replace_lyrics`	No
`can_update_visuals`	No
`visual_preferences`	No
`needs_lyrics_review`	No
`lyrics_search_outcome`	No
`lyrics_search_provider`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 13, 2026

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"
+]

First observedNov 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false) by disclosing the real side effect — reserving the existing account balance — and that processing runs in the background. It also explains the retry contract: reuse the same idempotency key after a lost response, which reconciles the non-idempotent hint with safe retries rather than contradicting it.

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?

Dense but front-loaded: the confirmation precondition comes first, then the side effect, then the retry rule, then the post-call monitoring loop. Every sentence carries information, though the monitoring/follow-up block runs long and could be tightened without losing meaning.

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?

For a destructive, balance-reserving launch with five parameters and an output schema, the definition covers the confirmation gate, side effects, retry semantics and the required follow-up loop. What is missing is failure-mode guidance for revision conflicts or insufficient balance, which an agent would have to discover from the output schema or errors.

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%, so the description must carry parameter meaning; it maps 'current quote and revision' to quote_id/expected_revision, explains idempotency_key's retry role, and ties visual_preferences to user confirmation. However it never explains what expected_revision protects against (concurrent modification, revision mismatch failure) or what project_id scoping means, leaving the two most semantically loaded fields partly opaque.

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 with scope: 'Start the quoted Quick karaoke' tied to an existing quote, which clearly separates it from prepare_karaoke (which presumably produces the quote) and retry_karaoke. An agent can identify the operation and its precondition without opening the 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?

Explicit when-to-use gate ('only after the user explicitly confirms its current price and visual preferences'), plus routing to siblings: monitor with get_karaoke in the same turn, open show_karaoke only when the MP4 is ready. It also names anti-patterns ('do not finish with only a launch receipt or ask the user to request another status check'), which is rare and valuable guidance.

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

All karaoke-maker-3000 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?