Skip to main content
Glama

set_arrangement_time

Idempotent

Set the Arrangement playhead to a specific beat to determine where playback starts, and read back the confirmed position. Accepts fractional beats for precise timing.

Instructions

Move the Arrangement playhead to a beat and read the position back.

Writes ``song.current_song_time``. This moves where playback would start. It
does not start it. Use play to begin, or play with ``from_beat`` to do both in
one call.

Returns:
    Dictionary with the write confirmation and the read-back song time.

Note:
    Do not sample a moving transport through lom_batch. A read that follows a
    jump inside the same batch still reports the position from before the move,
    and it reports it without an error (see lom_batch). One call per position.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
at_beatYesPosition on the Arrangement timeline in beats from the start, where beat 0 is the beginning of the song. Fractional beats are accepted, so 33.5 is the second half of bar 9 in 4/4.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / at_beat / description
      Added value: +"Position on the Arrangement timeline in beats from the start, where beat 0 is the beginning of the song. Fractional beats are accepted, so 33.5 is the second half of bar 9 in 4/4."
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

The description discloses that it writes song.current_song_time, that it moves the playhead without starting playback, and includes a specific caveat about batch reads reporting stale positions. This goes beyond the annotations by explaining side effects and edge cases.

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 tight and well-organized: a clear main action, a brief elaboration on the side effect, an alternative guidance, and a note about batching. No redundant information.

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

Completeness5/5

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

For a simple one-parameter tool, the description covers the action, side effects, alternatives, and a critical batch caveat. It provides enough context for an agent to decide when and how to call it correctly.

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?

The single parameter 'at_beat' has a thorough schema description covering fractional beats and bar references, fully clarifying its meaning. The tool description also reinforces its purpose by mentioning 'to a beat'.

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 clearly states the action ('Move the Arrangement playhead to a beat') and the resource ('Arrangement playhead'), with an additional readback. It also distinguishes this tool from 'play' and 'play with from_beat' by explaining what it does not do (start playback).

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool versus alternatives: 'Use play to begin, or play with from_beat to do both in one call.' The note about lom_batch further advises against using it in batch scenarios, providing clear usage context.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/romanstark/live-maestro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server