Plan, check and analyze a song
songPlans and analyzes a song written in MTL text (render checks too); returns a share link that plays it in the browser (90 days, no render). Stages: plan, write, light analysis loop, one deep analysis, fix; then the share link to listen; one render only when the user asks for an audio file. song(plan) gives a skeleton; analyze:true: light (repeatable); deep:true: measured (once). Your own sound: i3 - name="Glass Lead" wave=saw cutoff=55 (a quoted word after iN is a preset); tracks play it as i3. The syntax: describe(topic="syntax") gives the core grammar and a list of sections, each read with q (q="synth" every synth field, q="arp", q="modulation" ...). Stopping a note: = releases it (its release plays out); an ECx effect cuts it dead after x ticks (_!EC0 on that step, D4!EC3 on the note). Each reply has a songId: send ref instead of the text again, with layers for batch edits (tracks, instruments, mix, order). It warns when a song is longer than one audio file holds (WAV about 8 min, Ogg or Opus longer). To work on a song in another program, convert it to MIDI or a tracker module. 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": "song"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| len | No | Target seconds | |
| mtl | No | Song in MTL text (describe topic=mtl). Kept 2 hours as a working copy: later calls can send ref (the songId) instead. | |
| ref | No | Instead of mtl: a songId from an earlier reply (kept 2 hours), a render asset id, or a share link | |
| alts | No | Other MTL versions to rank by score | |
| deep | No | With analyze: deep analysis, a measured analysis-only render. Suited to once or twice when the song is nearly done | |
| loop | No | Should loop | |
| plan | No | Alone: {bpm, meter, key, peak, sections:[{id, bars, energy 1-5, role}], mix?} gives a skeleton, timing, checks | |
| check | No | Same as analyze | |
| genre | No | Scores against this genre's factors (each genre scores its own); describe(topic="genres") | |
| range | No | With analyze: one section, e.g. "2" or "2-3" (order entries) | |
| style | No | Voice palette; default chip | |
| energy | No | Planned 1-5 per order entry, for check:true | |
| intent | No | Deliberate choices, not scored | |
| layers | No | With mtl or ref: batch edits {add:["A: 3 i3 v40: C4 . . ."], replace, remove:["A:3"], instruments, mix, notes, order}; returns the edited song | |
| return | No | mtl echoes the song back | |
| voices | No | List these instruments' settings | |
| analyze | No | Light analysis: no audio, instant, free. Suited to every edit | |
| compare | No | With analyze: A/B against an earlier songId, asset id or share link | |
| compose | No | Instead of mtl: {bpm, form, chords, parts:[{id,gen}]}. describe(topic="generators") | |
| skip_plan | No | Reason to skip research and plan for a full song (else they come first) |