Skip to main content
Glama

write_progression

Writes a chord progression from roman numerals or a style into an empty Session slot or existing clip, adding voice leading and an accompaniment pattern.

Instructions

Write a chord progression into an empty Session slot (clip created to fit) or an existing clip, voiced with smooth voice leading and played with an accompaniment pattern.

Give numerals (roman numerals in the key: "ii7", "V7", "Imaj7", "bVII", "iv", "V/V", "N6", "viiø7"...) or a style (its typical progression number progression_index, its scale and pattern are used unless given). Patterns: block, pulse, pulse8, offbeat, arp8, arp16, alberti, bossa, waltz, ballad, stabs.

Parameters:

  • track_index / clip_index: Target MIDI track and Session slot

  • root: Key tonic ("C", "F#", "Bb")

  • scale: Scale/mode of the key (default major)

  • numerals: Roman numerals (optional if style)

  • style: Style name (see music_styles)

  • progression_index: Which of the style's progressions

  • beats_per_chord: Harmonic rhythm (4 = one chord per bar)

  • pattern: Accompaniment pattern (default: the style's first, else block)

  • low / high: Range of the chord voicings

  • bass: Add a bass line (root, an octave or two below)

  • repeat: Times to repeat the progression

  • voices: Notes per chord voicing (3-5)

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": {
      "track_index": "<track_index>",
      "clip_index": "<clip_index>",
      "root": "<root>"
    },
    "name": "write_progression"
  }
}

Input Schema

NameRequiredDescriptionDefault
lowNoE3
bassNo
highNoG4
rootYes
scaleNomajor
styleNo
repeatNo
voicesNo
patternNo
numeralsNo
clip_indexYes
track_indexYes
beats_per_chordNo
progression_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that a clip is created to fit an empty slot or that an existing clip is targeted, and it describes voicing and accompaniment behavior, but it does not clarify whether existing clip content is overwritten, what happens on failure, or whether the operation is undoable.

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

Conciseness5/5

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

The description is front-loaded with the core action, then moves into input selection guidance and an organized parameter list. Its length is justified by the 14-parameter complex tool, and every sentence contributes useful information.

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 complex mutation tool with no annotations and 0% schema coverage, the description is largely complete: it covers purpose, parameters, defaults, and patterns. It still leaves out overwrite semantics and sibling-tool routing, but return values are covered by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 compensate, and it does: it explains all 14 parameters, including examples for `numerals`, the list of `pattern` values, harmonic rhythm for `beats_per_chord`, and defaults for scale, bass, repeat, and voices. This adds substantial meaning beyond the bare 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 states a specific verb and resource: it writes a chord progression into an empty Session slot or existing clip, with voice leading and accompaniment. This clearly distinguishes it from general note-adding or clip-creation tools by focusing on generated harmonic content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the choice between `numerals` and `style`, notes that `numerals` is optional when `style` is supplied, and gives defaults for patterns. However, it does not state when to use this tool versus alternatives such as `add_notes_to_clip` or `create_clip`, nor does it describe when not to use it.

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

Deploy Server

Other Tools