Skip to main content
Glama

record_arrangement

Records armed tracks into the Arrangement between start and end beat positions, moving the playhead and stopping recording at the end time; arm tracks first.

Instructions

Record the armed tracks into the Arrangement between two song positions (in beats): moves the playhead, turns Arrangement Record on, plays, and stops at end_time. Arm tracks first (set_track_arm).

Parameters:

  • start_time: Song position to start at (beats)

  • end_time: Song position to stop at (beats)

  • wait: Block until the recording ends (default) or return at once (then poll get_recording_status)

  • max_wait_seconds: Safety limit when waiting; recording is stopped past it

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": {
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "record_arrangement"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo
end_timeYes
start_timeYes
max_wait_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations to rely on, the description still discloses meaningful side effects: it moves the playhead, turns Arrangement Record on, plays, and stops at end_time, and max_wait_seconds acts as a safety cutoff. It leaves unclear whether existing material in the range is overwritten, whether recording state is restored afterwards, and what happens if no tracks are armed.

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 core behavior and its side-effect sequence are front-loaded in the first sentence, followed by a compact parameter glossary. No sentence is filler; each line adds operational detail.

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 multi-step, state-changing operation with no annotations, the description covers preconditions, side effects, blocking semantics, and the fallback polling path. The main remaining gap is overwrite/failure semantics within the recorded range, which matters for a destructive-ish capture operation; 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 carries the full burden and does so: it defines start/end times in beats, explains that wait blocks or returns immediately and points to get_recording_status for polling, and characterizes max_wait_seconds as a safety limit. All four parameters gain meaning beyond the bare typed fields.

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 names a specific action and target: 'Record the armed tracks into the Arrangement between two song positions (in beats)'. It further clarifies scope by stating it only records armed tracks, which distinguishes the action from related utilities such as stop_arrangement_recording and get_recording_status.

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

Usage Guidelines4/5

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

The description gives an explicit precondition ('Arm tracks first (set_track_arm)') and a clear alternative behavior for wait=false ('then poll get_recording_status'). It does not state when-not to use the tool or warn about conditions such as no armed tracks, so the guidance is strong but not exhaustive.

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