Skip to main content
Glama
romanstark

Dorico Maestro

by romanstark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

playback

Idempotent

Start, stop, or rewind Dorico's transport to hear your composition from the playhead, selection, or flow start.

Instructions

Start, stop or rewind Dorico playback.

Transport only: no note, dynamic or layout changes as a result.

Returns:
    Result dictionary reporting whether the transport command was accepted.

Note:
    Playback is the one way to hear whether a write landed, since kOK proves
    only that the command was accepted (docs/protocol.md, 'Command Acceptance
    vs Effect'). It makes sound, which matters if a person is in the room.

    Use navigate to scroll the score without playing, and goto_bar to move the
    caret. Neither of those moves the playhead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoWhat the transport should do: 'play', 'stop' or 'rewind'.play
locationNoWhere playback starts from, read only when action is 'play': 'kPlayhead' from the playhead, 'kSelection' from what is selected, 'kStartOfFlow' from the top, 'kLastStartPosition' from wherever the last play began.kPlayhead

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / action / description
      Added value: +"What the transport should do: 'play', 'stop' or 'rewind'."
    • addedInput schema / properties / location / description
      Added value: +"Where playback starts from, read only when action is 'play': 'kPlayhead' from the playhead, 'kSelection' from what is selected, 'kStartOfFlow' from the top, 'kLastStartPosition' from wherever the last play began."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/destructive/idempotent hints, the description discloses the bounded side-effect surface ('no note, dynamic or layout changes'), the audible side effect ('It makes sound'), and the semantics of the Result dictionary ('reporting whether the transport command was accepted'). It even adds the important acceptance-vs-effect nuance around kOK, which is valuable for an agent.

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 action and constraints are front-loaded, the Returns note is separated, and the following Note earns its place by explaining user-visible side effects and sibling routing. No redundancy or filler.

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 two-optional-parameter transport tool with an output schema, the description covers purpose, safety boundaries, return semantics, audible side effects, and alternatives. An agent has everything needed to invoke it correctly.

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

Parameters3/5

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

The schema already fully documents both parameters with 100% coverage, so the description adds little parameter-level meaning; 'start, stop or rewind' merely restates the action enum. The baseline 3 applies because the description does not need to compensate for schema gaps.

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 opens with a specific action set ('Start, stop or rewind Dorico playback') and scopes the tool to 'Transport only', explicitly disclaiming note, dynamic, or layout changes. It further distinguishes itself by naming navigate and goto_bar as non-audible alternatives, so an agent can pick the right sibling without guessing.

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?

It explicitly names the alternatives: 'Use navigate to scroll the score without playing, and goto_bar to move the caret', and states that neither moves the playhead. It also gives a concrete reason to prefer playback — 'the one way to hear whether a write landed' — making the when-to-use decision explicit.

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