Skip to main content
Glama

Render a song to audio

render
Idempotent

Produces WAV, Ogg or Opus files: the audio file a user asks for, to download or to embed in a game, app, presentation or video. A request for a song, a tune or music needs no file: song's share link plays it in the browser (the share link plays it, no render), and each render counts against the hourly render quota. Send mtl, ref (a songId) or compose; it checks the song itself (syntax: describe(topic="syntax"), sections by q). One file holds about 8 min as WAV (about 5 at 24-bit 48 kHz), longer as Ogg or Opus; a longer request is refused with the exact limit. len gives exact seconds; loop:true adds seamless loop points; stems:true gives one file per instrument role (@lead, @bass, @drums...); adaptive:true gives a zip of same-length looping layers in intensities, stingers from extra cues, a manifest, a Web Audio player and Godot, Unity, FMOD and Wwise notes; cues renders named sections. A long render replies rendering with asset ids, and assets(ids) gives the links when done. Files last 2 h; https://moosetracker.app/acceptable-use.html Schema a964948f.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render"
  }
}

Input Schema

NameRequiredDescriptionDefault
cueNo
lenNoExact seconds: a short song repeats its order (said in the result), a long one fades out; never silence
mtlNoSong in MTL text (describe topic=mtl). Kept 2 hours as a working copy: later calls can send ref (the songId) instead.
refNoInstead of mtl: a songId from an earlier reply (kept 2 hours), a render asset id, or a share link
zipNo
bitsNoWAV bits
cuesNoOne file per cue
loopNoSeamless loop plus loop points
peakNoPeak dBFS
rateNoHz
tailNoRing-out seconds
genreNoFor the score check
rangeNoOrder positions only, e.g. "2-4"
stemsNoOne file per role
styleNoVoice palette; default chip
detailNoAdds score, per-section loudness and MIX flags with fixes
formatNoDefault wav; ogg = Vorbis 44.1 kHz; opus = Ogg Opus 48 kHz
composeNoInstead of mtl: {bpm, form, chords, parts:[{id,gen}]}. describe(topic="generators")
previewNoOne section (range, default 1), ≤20 s Opus, light quota, MIX flags
adaptiveNoA zip of same-length looping layers grouped into intensities (default calm, tense, full; set your own with adaptive.levels), stingers from extra cues, manifest.json, a Web Audio player and setup notes for Godot, Unity, FMOD and Wwise (describe topic=loops)
auditionNoHear one channel alone as a preview; try swaps its sound: {ch:3, try:"i3 \"Warm Pad\""}
loudnessNo
skip_reviewNoReason to skip a full song's deep review (else it comes first)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 826121bd"New value: +"Schema a964948f"
  2. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d544474"New value: +"Schema 826121bd"
  3. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0781812e"New value: +"Schema 2d544474"
  4. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0d11f08d"New value: +"Schema 0781812e"
  5. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d7abb8b"New value: +"Schema 0d11f08d"
  6. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema ff675289"New value: +"Schema 2d7abb8b"
    • addedInput schema / properties / adaptive
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "levels": {
      +          "additionalProperties": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "description": "Your own intensities in order, each a list of roles: {\"explore\":[\"pad\"],\"fight\":[\"pad\",\"bass\",\"drums\",\"lead\"]}",
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  ],
      +  "description": "A zip of same-length looping layers grouped into intensities (default calm, tense, full; set your own with adaptive.levels), stingers from extra cues, manifest.json, a Web Audio player and setup notes for Godot, Unity, FMOD and Wwise (describe topic=loops)"
      +}
  7. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema 2a55f659"New value: +"Schema ff675289"
    • changedInput schema / properties / len / maximum
      Previous value: -180New value: +5928
  8. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema 71227a86"New value: +"Schema 2a55f659"
    • addedInput schema / properties / skip_review
      Added value: +{
      +  "description": "Reason to skip a full song's deep review (else it comes first)",
      +  "type": "string"
      +}
  9. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 64bfe66c"New value: +"Schema 71227a86"
  10. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema eb59845f"New value: +"Schema 64bfe66c"
    • addedInput schema / properties / genre / enum
      Added value: +[
      +  "chiptune",
      +  "chip-battle",
      +  "game-overworld",
      +  "game-battle",
      +  "game-town",
      +  "game-dungeon",
      +  "game-menu",
      +  "game-victory",
      +  "game-racing",
      +  "game-horror",
      +  "jrpg",
      +  "classical",
      +  "baroque",
      +  "fugue",
      +  "minuet",
      +  "romantic",
      +  "march",
      +  "waltz",
      +  "nocturne",
      +  "lullaby",
      +  "hymn",
      +  "carol",
      +  "jazz",
      +  "bebop",
      +  "cool-jazz",
      +  "swing",
      +  "big-band",
      +  "dixieland",
      +  "ragtime",
      +  "bossa-nova",
      +  "smooth-jazz",
      +  "fusion",
      +  "jazz-ballad",
      +  "gypsy-jazz",
      +  "blues",
      +  "slow-blues",
      +  "jump-blues",
      +  "shuffle",
      +  "soul",
      +  "gospel",
      +  "rnb",
      +  "funk",
      +  "disco",
      +  "rock",
      +  "hard-rock",
      +  "blues-rock",
      +  "punk",
      +  "pop-punk",
      +  "metal",
      +  "prog-rock",
      +  "ska",
      +  "pop",
      +  "synth-pop",
      +  "power-pop",
      +  "dance-pop",
      +  "power-ballad",
      +  "kpop",
      +  "musical-theater",
      +  "country",
      +  "bluegrass",
      +  "folk",
      +  "celtic",
      +  "sea-shanty",
      +  "polka",
      +  "reggae",
      +  "salsa",
      +  "samba",
      +  "tango",
      +  "latin-pop",
      +  "house",
      +  "techno",
      +  "trance",
      +  "edm",
      +  "synthwave",
      +  "vaporwave",
      +  "dubstep",
      +  "drum-and-bass",
      +  "breakbeat",
      +  "trap",
      +  "hip-hop",
      +  "boom-bap",
      +  "lofi",
      +  "chillout",
      +  "ambient",
      +  "drone",
      +  "new-age",
      +  "industrial",
      +  "cinematic",
      +  "epic",
      +  "suspense",
      +  "horror",
      +  "fantasy",
      +  "western",
      +  "spy",
      +  "sci-fi",
      +  "world",
      +  "afrobeat",
      +  "klezmer",
      +  "bollywood"
      +]
  11. Changed4 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema 3b8fe45c"New value: +"Schema eb59845f"
    • addedInput schema / properties / audition
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Hear one channel alone as a preview; try swaps its sound: {ch:3, try:\"i3 \\\"Warm Pad\\\"\"}",
      +  "properties": {
      +    "ch": {
      +      "maximum": 16,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "try": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "ch"
      +  ],
      +  "type": "object"
      +}
    • changedInput schema / properties / mtl / description
      Previous value: -"Song in MTL text (describe topic=mtl). Send it whole each time; we keep none."New value: +"Song in MTL text (describe topic=mtl). Kept 2 hours as a working copy: later calls can send ref (the songId) instead."
    • addedInput schema / properties / ref
      Added value: +{
      +  "description": "Instead of mtl: a songId from an earlier reply (kept 2 hours), a render asset id, or a share link",
      +  "type": "string"
      +}
  12. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 9b20e675"New value: +"Schema 3b8fe45c"
  13. Changed5 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema 415a8741"New value: +"Schema 9b20e675"
    • addedInput schema / properties / bits
      Added value: +{
      +  "default": 16,
      +  "description": "WAV bits",
      +  "enum": [
      +    16,
      +    24
      +  ],
      +  "type": "integer"
      +}
    • changedInput schema / properties / detail / description
      Previous value: -"Add length guide and score check"New value: +"Adds score, per-section loudness and MIX flags with fixes"
    • addedInput schema / properties / preview
      Added value: +{
      +  "description": "One section (range, default 1), ≤20 s Opus, light quota, MIX flags",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / rate
      Added value: +{
      +  "default": 44100,
      +  "description": "Hz",
      +  "enum": [
      +    44100,
      +    48000
      +  ],
      +  "type": "integer"
      +}
  14. Changed5 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema d568427c"New value: +"Schema 415a8741"
    • changedInput schema / properties / len / description
      Previous value: -"Exact length in seconds: a short song is extended by repeating its order, a long one fades out at len. Never padded with silence."New value: +"Exact seconds: a short song repeats its order (said in the result), a long one fades out; never silence"
    • addedInput schema / properties / peak
      Added value: +{
      +  "description": "Peak dBFS",
      +  "maximum": 0,
      +  "minimum": -30,
      +  "type": "number"
      +}
    • addedInput schema / properties / range
      Added value: +{
      +  "description": "Order positions only, e.g. \"2-4\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / tail
      Added value: +{
      +  "description": "Ring-out seconds",
      +  "maximum": 4,
      +  "minimum": 0,
      +  "type": "number"
      +}
  15. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 90ddc268"New value: +"Schema d568427c"
  16. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"Schema 90ddc268"
  17. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive, idempotent, non-read-only call; the description adds quota consumption per render, hard duration limits ("about 8 min as WAV, about 5 at 24-bit 48 kHz") with explicit refusal behavior, 2-hour file retention, async rendering with asset ids, and a link to acceptable-use terms. That is substantial disclosure beyond the annotations. It does not say what an immediate (non-async) reply looks like or how failures other than length-limit are surfaced.

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?

It front-loads the purpose well, but the body is a single semicolon-choked block whose clauses are hard to parse, and some parenthetical asides ("(syntax: describe(topic=\"syntax\"), sections by q)") are cryptic. The content mostly earns its place, but the structure taxes the reader.

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 23-parameter, zero-required-parameter tool with nested objects, no output schema, and thin annotations, the description supplies the lifecycle (quota, expiration, async polling via assets) that would otherwise be missing. It stops short of describing the synchronous return payload or error shapes, which an agent would still want.

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 already 87%, so the baseline is 3; the description goes further by explaining what several flags produce in combination — stems as "one file per instrument role (@lead, @bass, @drums...)", adaptive as "same-length looping layers in intensities, stingers from extra cues, a manifest, a Web Audio player and Godot, Unity, FMOD and Wwise notes", and cues as "named sections". Minor params (peak, tail, bits, rate, audition, skip_review, loudness) are left to 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?

States a concrete verb+resource ("Produces WAV, Ogg or Opus files") plus the user goal (download or embed in game, app, presentation, video), and explicitly contrasts with the song/share-link path: "the share link plays it, no render." An agent can separate this from the sibling `song` tool without opening either 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 explicit routing rules: when no render is needed (listening via share link), the three input paths (mtl, ref, or compose), lighter-weight `preview` and `detail` options, and the async follow-up path (long render replies `rendering`, then `assets(ids)`). It also points to `describe(topic="syntax")` for input syntax, so the agent is not left to guess.

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