Skip to main content
Glama

Sats4AI - Bitcoin-Powered AI Tools

by io.github.cnghockey
OverviewDiscussionsAdmin

generate_music

Generate a full song with AI vocals from a style prompt plus lyrics — or an INSTRUMENTAL bed / underscore (background music under video narration, intros, outros) by sending ONLY structure tags and no words. You choose the length: 15-300 seconds at 5 sats/second (75-1500 sats). Specify BPM, key, genre, mood in prompt. Returns a 44.1 kHz 16-bit stereo WAV URL. Structure tags must each be on their OWN line — words on a tag line are DROPPED by the model, which silently shortens the song. Don't want to write lyrics? Set lyricsAddon:true (+25 sats) and optionally lyricsAbout to say what they should be about. Pay per request with Bitcoin Lightning — no API key or signup needed. Requires create_payment with toolName='generate_music' AND the same duration (the price is bound to it).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lyricsNoSong lyrics with section tags (up to 3,500 chars). Each tag on its OWN line, words on the lines after it — words sharing a line with a tag are dropped. Tags: [intro], [verse], [pre-chorus], [chorus], [post-chorus], [bridge], [instrumental], [solo], [outro]. Send only tags and no words for an instrumental.
promptYesMusic style with BPM, key, genre, mood, instruments (up to 2,000 chars). Example: 'E minor, 90 BPM, acoustic guitar ballad, male vocal'
modelIdNoOptional. Omit for default model.
durationNoSong length in seconds, 15-300. THE PRICE (5 sats/second) — must match the duration sent to create_payment. Default: 15
paymentIdYesValid payment ID (must be paid)
lyricsAboutNoOptional, with lyricsAddon: what the lyrics should be about. Omit and the subject is inferred from your music prompt.
lyricsAddonNoSet true to have the lyrics written for you (+25 sats, billed on the song's own invoice). Must also be sent to create_payment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / properties / audio_format
      Removed value: -{
-  "description": "Output format. Default: mp3",
-  "enum": [
-    "mp3",
-    "wav",
-    "pcm"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / bitrate
      Removed value: -{
-  "description": "Audio bitrate. Default: 256000",
-  "enum": [
-    32000,
-    64000,
-    128000,
-    256000
-  ],
-  "type": "integer"
-}
    • addedInput schema / properties / duration
      Added value: +{
+  "description": "Song length in seconds, 15-300. THE PRICE (5 sats/second) — must match the duration sent to create_payment. Default: 15",
+  "type": "integer"
+}
    • removedInput schema / properties / is_instrumental
      Removed value: -{
-  "description": "Set true for instrumental-only (no vocals). When true, prompt is required, lyrics are ignored.",
-  "type": "boolean"
-}
    • changedInput schema / properties / lyrics / description
      Previous value: -"Song lyrics with section tags (up to 3,500 chars). Tags: [Intro], [Verse], [Pre Chorus], [Chorus], [Bridge], [Outro], [Solo], [Hook], [Drop], [Build Up], [Inst], [Interlude], [Transition], [Break], [Post Chorus]"New value: +"Song lyrics with section tags (up to 3,500 chars). Each tag on its OWN line, words on the lines after it — words sharing a line with a tag are dropped. Tags: [intro], [verse], [pre-chorus], [chorus], [post-chorus], [bridge], [instrumental], [solo], [outro]. Send only tags and no words for an instrumental."
    • addedInput schema / properties / lyricsAbout
      Added value: +{
+  "description": "Optional, with lyricsAddon: what the lyrics should be about. Omit and the subject is inferred from your music prompt.",
+  "type": "string"
+}
    • addedInput schema / properties / lyricsAddon
      Added value: +{
+  "description": "Set true to have the lyrics written for you (+25 sats, billed on the song's own invoice). Must also be sent to create_payment.",
+  "type": "boolean"
+}
    • removedInput schema / properties / lyrics_optimizer
      Removed value: -{
-  "description": "Set true to auto-generate lyrics from prompt when lyrics are empty.",
-  "type": "boolean"
-}
    • removedInput schema / properties / sample_rate
      Removed value: -{
-  "description": "Audio sample rate. Default: 44100",
-  "enum": [
-    16000,
-    24000,
-    32000,
-    44100
-  ],
-  "type": "integer"
-}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries full behavioral disclosure: it reveals pricing (5 sats/second), output format (44.1 kHz 16-bit stereo WAV URL), the silent lyric-dropping behavior on tag lines, and the payment binding requirement. No contradictions with annotations (none exist).

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?

The description is long but every sentence adds value: it covers purpose, modes, pricing, constraints, payment flow, and return format. It is front-loaded with the core action and then provides necessary details. Slightly dense but not bloated.

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?

Given 7 parameters, a payment dependency, and no output schema, the description is remarkably complete: it explains the return format, the tag syntax pitfall, pricing, duration limits, and the create_payment correlation. Nothing an agent needs to call it correctly 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?

Schema coverage is 100%, so baseline is 3, but the description adds meaningful cross-parameter context such as the price binding to duration and the requirement that lyricsAddon also be sent to create_payment. This goes beyond the individual parameter descriptions in the schema.

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?

The description clearly states a specific action ('Generate a full song') with distinct modes (vocals vs instrumental), and it differentiates itself from sibling generate_* tools by specifying music-specific outputs and the payment model. The verb and resource are unambiguous.

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?

Provides explicit instructions on when to use lyrics vs instrumental tags, when to enable lyricsAddon, and the required create_payment prerequisite with matching duration. It also covers the optional lyricsAbout flow, leaving no ambiguity about invocation.

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

All Sats4AI - Bitcoin-Powered AI Tools 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