Skip to main content
Glama

set_arrangement_time

Move the playhead to a specific beat position to control playback and navigate arrangements precisely.

Instructions

Move the playhead.

Parameters:

  • time: Song position in beats (0 = start; in 4/4, bar N starts at 4 × (N − 1))

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": {
      "time": "<time>"
    },
    "name": "set_arrangement_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about whether the playhead move takes effect during playback or recording, whether it requires the transport to be stopped, or whether the position is quantized to bars. For a transport mutation, that is a meaningful gap.

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?

Front-loaded with the action in four words, then a single scoped parameter note. No filler, no restating the tool name, and the format makes the one input easy to locate.

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

Completeness3/5

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

The tool is simple (one required number) and ships an output schema, so return values need no explanation. However, the absence of annotations means the description should at least state the transport state assumptions and any effect on playback; that is the missing piece for a complete definition.

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 0% and the schema only says 'number', so the description must compensate — and it does, defining the unit (beats), the origin (0 = start), and the conversion for bar positions in 4/4. It leaves open whether fractional beats are accepted and what happens with negative values, so it is short of exhaustive.

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?

States a specific verb and resource: "Move the playhead." Combined with the name set_arrangement_time, an agent can tell this repositions the arrangement position rather than editing clips or tracks. It stops short of naming any sibling it must be distinguished from, but the purpose itself is unambiguous.

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?

Gives implied context through the parameter note (0 = start, bar math in 4/4), which tells the agent what values are meaningful, but it never says when to call this versus tools like build_arrangement or switch_to_arrangement_view, nor any precondition such as whether playback is running.

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