Skip to main content
Glama

nanoodle

by io.github.nanoodlecom
OverviewDiscussionsAdmin

sing

Draft an original closing-credits song. One text model writes lyrics; Mureka Generate Song sings them using the editable musical style. Music step $0.225, plus text. Listen for clear words, melody … text:Song Instructions -> text:Musical style -> llm:Lyrics -> music:Song; returns audio (mureka-v9.5/generate-song) saved to disk (file path in result). Runs on NanoGPT — $0.55 deposit per call, paid in Nano (XNO) — settles at actual model cost + 20%, change returned; no account needed; last run $0.0497, ~1m 56s. Example: Audio sample (https://nanoodle.com/examples/gallery/#sing). A 170-second generated closing-credits song. Gemini 3.8 Flash reported clear gentle acoustic vocals and a chorus matching the supplied lyrics. This is model-assisted audio review, not human listening sign-off.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
LyricsNoSystem prompt; default: "Write original singable lyrics from the brief, maximum 160 words. Plain language, concrete details, natural stresses ..."; optional
_payment_idNoPayment id from this tool's previous payment-required response. Phase 3 only: after /x402/watch closes with status paid, call again with the same arguments plus this id to open the RESULTS stream. Do not pass it while payment is still pending — monitor the watch SSE first.
Musical_styleNoText; default: "Gentle acoustic folk, relaxed mid-tempo, warm solo vocal, fingerpicked guitar, soft brushed percussion. Clear words a..."; optional
Song_InstructionsNoText; default: "Write a short original song for the closing credits of a cozy repair-shop game. Theme: fixing a small thing makes a h..."; optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / Bands
      Removed value: -{
-  "description": "Text; default: \"Bands liked:\\nPortishead, Massive Attack, Tricky\"; optional",
-  "type": "string"
-}
    • addedInput schema / properties / Lyrics
      Added value: +{
+  "description": "System prompt; default: \"Write original singable lyrics from the brief, maximum 160 words. Plain language, concrete details, natural stresses ...\"; optional",
+  "type": "string"
+}
    • addedInput schema / properties / Musical_style
      Added value: +{
+  "description": "Text; default: \"Gentle acoustic folk, relaxed mid-tempo, warm solo vocal, fingerpicked guitar, soft brushed percussion. Clear words a...\"; optional",
+  "type": "string"
+}
    • changedInput schema / properties / Song_Instructions / description
      Previous value: -"Text; default: \"Write a late-night 90s trip-hop torch song set under the last lit vermillion torii at Fushimi Inari, 3:17am. A rusted...\"; optional"New value: +"Text; default: \"Write a short original song for the closing credits of a cozy repair-shop game. Theme: fixing a small thing makes a h...\"; optional"
    • removedInput schema / properties / Style_System_Prompt
      Removed value: -{
-  "description": "Text; default: \"You invent a musical style that fits the given lyrics. Reply with only the style, richly descriptive — no commentary....\"; optional",
-  "type": "string"
-}
    • removedInput schema / properties / System_prompt
      Removed value: -{
-  "description": "System prompt; default: \"You are an award-winning songwriter. Write only the lyrics — no title, no commentary, no explanations.\\nPrinciples:\\n- ...\"; optional",
-  "type": "string"
-}
    • removedInput schema / properties / System_prompt_2
      Removed value: -{
-  "description": "System prompt; default: \"Negate the style — what would go poorly, the worst you can imagine. No preamble or postamble.\"; optional",
-  "type": "string"
-}
  2. Changed3 schema fields changed
    • changedInput schema / properties / Bands / description
      Previous value: -"Text; default: \"Bands liked:\\nSoundgarden, XX\"; optional"New value: +"Text; default: \"Bands liked:\\nPortishead, Massive Attack, Tricky\"; optional"
    • changedInput schema / properties / Song_Instructions / description
      Previous value: -"Text; default: \"Write a wistful 90s trip-hop track about the singularity.\"; optional"New value: +"Text; default: \"Write a late-night 90s trip-hop torch song set under the last lit vermillion torii at Fushimi Inari, 3:17am. A rusted...\"; optional"
    • changedInput schema / properties / System_prompt_2 / description
      Previous value: -"System prompt; default: \"Negate the style - what would go poorly,  the worst you can imagine. No preamble or postamble.\"; optional"New value: +"System prompt; default: \"Negate the style — what would go poorly, the worst you can imagine. No preamble or postamble.\"; optional"
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden, and it delivers: it discloses the multi-step workflow, that the result is audio saved to disk with a file path, the NanoGPT payment/deposit model, estimated cost and runtime, no-account requirement, and that audio quality review is model-assisted rather than human sign-off.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Purpose and pipeline are front-loaded, which is good, but the description is a long, dense paragraph including volatile details like last-run cost and duration, plus a Gemini quality report. These add context but make it less concise than it could be.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and no annotations, the description is very complete: it covers workflow, return value and file path, payment mechanics, cost and runtime expectations, an example, and a caveat about audio review. Nothing essential for invoking the tool is missing.

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?

The schema already documents all parameters with 100% coverage, so the baseline is 3. The description adds value by showing the pipeline order and how the parameters interact: text instructions and musical style feed into LLM-written lyrics, which are then sung by the music model.

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 purpose: drafting an original closing-credits song, and clarifies that actual audio is produced by Mureka Generate Song. It describes the full pipeline from lyrics to sung audio, so an agent knows exactly what the tool delivers and how it differs from the visual-art sibling tools.

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?

The description clearly implies when to use it: whenever an original closing-credits song with editable musical style is needed. It does not explicitly list exclusions or alternative tools, but the sibling tools are all image/video-focused, so the intended use is evident.

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

All nanoodle toolsInspect
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