karaoke-maker-3000

Prepare karaoke

prepare_karaoke

Import the user's selected MP3 and prepare a free Quick draft with a price quote. In ChatGPT, use this native file-parameter route first: audio_file receives the real host-provided download_url and file_id, and this server downloads the file. Do not invent file references or choose raw sandbox upload merely because an attachment is readable; raw upload additionally requires supported outbound HTTPS PUT. No processing starts. Discuss the returned price and visual wishes in the conversation, without opening a card. Use only a file the user selected for this task.

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": {
      "audio_file": "<audio_file>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "prepare_karaoke"
  }
}

Input Schema

Name	Required	Default
`title`	No
`artist`	No
`language`	No	auto
`audio_file`	Yes
`idempotency_key`	Yes

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

A3.7/5.0

Behavior3/5

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

Adds real value beyond the annotations: 'No processing starts' clarifies this is only a quote/draft step despite openWorldHint and destructiveHint=false, and it discloses that the server performs the download. It does not address the idempotency_key parameter or retry semantics, which is notable given idempotentHint=false on a tool that accepts an idempotency key.

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?

Well front-loaded: purpose first, then the routing rule, then the behavioral caveat, then next steps. Some sentences are dense with host-specific asides ('merely because an attachment is readable'), but each one carries a routing or behavior constraint rather than filler.

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 not be described, and the safety/routing picture is covered by both annotations and text. The remaining gap is the undocumented non-file parameters, which matters for a tool nobody can call correctly without supplying an idempotency key.

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 parameter meaning, yet it only explains audio_file (that it receives host-provided download_url and file_id). The four other parameters (title, artist, language, idempotency_key) get no explanation at all, leaving an agent to guess what the idempotency key must contain and how language defaults behave.

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: imports the user's selected MP3 and produces a free 'Quick draft' with a price quote. It also implicitly distinguishes this route from a raw sandbox upload path, so an agent can tell what this tool is for without reading the schema. It stops short of naming sibling tools like get_karaoke or start_karaoke as follow-ups.

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?

Explicitly says to use this native file-parameter route first and names the alternative (raw sandbox upload) together with the condition that selects it (requires supported outbound HTTPS PUT). It also gives a negative rule ('Do not invent file references'), a scope rule ('Use only a file the user selected for this task'), and post-call guidance to discuss price in conversation rather than opening a card.

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?