Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

write_named_progression

Destructive

Write a named chord progression from the library into any key and clip, choosing voicing style, pattern and tempo. Use it to turn a progression name into playable chords on a track.

Instructions

Write a progression from the library (find_progressions) in any key, e.g. name="andalusian", key="A" -> Am G F E. style: close, open, spread, drop2, shell, rootless, quartal.

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>",
      "name": "<name>",
      "key": "<key>"
    },
    "name": "write_named_progression"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
nameYes
styleNoclose
centerNo
patternNoblock
velocityNo
clip_indexYes
track_indexYes
beats_per_chordNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, and the description does not add what gets overwritten, such as existing clip notes, or whether track_index/clip_index must point to existing objects. It adds the style choices and a naming example, but for a destructive write operation that is not enough behavioral context.

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 short and front-loaded, with the core action first and useful examples after. The style enumeration earns its place, though the notation is slightly cryptic.

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

Completeness2/5

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

For a destructive nine-parameter MIDI-writing tool, the description is materially incomplete: most parameters are unexplained and overwrite behavior is not disclosed. The output schema covers return values, but the input and side effects remain under-specified.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across nine parameters. The description explains only name, key, and the style values; it says nothing about required track_index and clip_index, nor about center, pattern, velocity, or beats_per_chord, so it fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: write a library progression in any key. It references find_progressions as the source and gives a concrete example, so the operation is clear, though it does not distinguish itself from the sibling write_progression tool.

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?

The mention of find_progressions implies a workflow: find a progression first, then write it. However, there is no explicit when-to-use guidance, no exclusion versus write_progression, and no prerequisites such as requiring an existing track or clip.

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