Skip to main content
Glama
romanstark

Dorico Maestro

write_score

Render a structured score spec into Dorico via caret entry or MusicXML import. Choose caret to add to the current flow, or MusicXML to include key and time signatures as a new flow.

Instructions

Render a ScoreSpec into Dorico by caret entry or MusicXML import.

The main way to write music here, and the one to reach for whenever there is
more than a single beat to enter: add_notes and add_rest do not chain, because
each re-enters note input at the caret and stacks on the same beat.

Returns:
    Result dictionary with the execution report, the preflight warnings, and the
    caveats attached to what was dispatched.

Note:
    Choose the method by what the score needs. 'caret' adds to the current flow
    and leaves the rest of the project alone, but it cannot set a key or time
    signature, because those go in through a popover no API can type into.
    'musicxml' carries them, at the price of arriving as a new flow rather than
    joining the current one.

    Call score_schema first for the exact shape: unknown keys are refused rather
    than ignored. Dorico must be in write mode, so use switch_mode if unsure.
    Nothing is verified by the return, since kOK means accepted rather than
    effective (docs/protocol.md), so check the result in the score.

    The caret path repositions between staves by jumping to the start of the
    flow, so it needs to know nothing about the flow's meter or length.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scoreYesThe score to work on, as a ScoreSpec object: metadata, parts, and the events inside them. Call score_schema first for the exact shape, which refuses unknown keys rather than ignoring them.
methodNoHow to get the music in. 'caret' types it into the flow already open, adding to what is there. 'musicxml' writes the whole score to a file and imports it as a new flow, which is the only path that carries key and time signatures.caret
preflightNoTrue runs the offline range and voice-leading checks first and reports what they found before anything is sent to Dorico. It warns rather than blocks.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed4 schema fields changedv0.1.5
    • changedInput schema / $defs / EventIn / properties / kind / description
      Previous value: -"'note', 'chord' or 'rest'; inferred if absent."New value: +"'note', 'chord' or 'rest'. Inferred if absent."
    • changedInput schema / $defs / EventIn / properties / staff / description
      Previous value: -"0-based; must match the nesting staff."New value: +"0-based. Must match the nesting staff."
    • changedInput schema / $defs / EventIn / properties / voice / description
      Previous value: -"1-based; must match the nesting voice."New value: +"1-based. Must match the nesting voice."
    • changedInput schema / $defs / VoiceIn / properties / index / description
      Previous value: -"1-based voice number; defaults to position."New value: +"1-based voice number, defaults to position."
  2. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / method / description
      Added value: +"How to get the music in. 'caret' types it into the flow already open, adding to what is there. 'musicxml' writes the whole score to a file and imports it as a new flow, which is the only path that carries key and time signatures."
    • addedInput schema / properties / preflight / description
      Added value: +"True runs the offline range and voice-leading checks first and reports what they found before anything is sent to Dorico. It warns rather than blocks."
    • addedInput schema / properties / score / description
      Added value: +"The score to work on, as a ScoreSpec object: metadata, parts, and the events inside them. Call score_schema first for the exact shape, which refuses unknown keys rather than ignoring them."
  3. Addedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations are sparse (only safe/write flags), so the description carries the burden. It discloses that kOK means accepted rather than effective, that the caret path restarts at the start of the flow, that musicxml imports as a new flow, and that unknown keys are refused rather than ignored. No contradiction with annotations.

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 long but every section earns its place: headline purpose, sibling differentiation, return summary, method decision rule, preconditions, and a subtle caret navigation behavior. It is structured with Returns and Note sections, making the density navigable.

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 complex write tool with no meaningful annotations, the description covers when to use it, how to choose the method, what side effects each method has, what preconditions exist, and how to interpret the return. Nothing an agent needs to call it correctly is missing.

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 100%, so the schema already documents score, method, and preflight. The description adds meaning beyond it: method choice tradeoffs, that preflight warns rather than blocks, and that score_schema should be called first because strict parsing rejects unknown keys. This is useful but not radically more than the schema already states.

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 first sentence names a specific verb ('Render') and resource ('ScoreSpec into Dorico') and immediately distinguishes the two entry paths, caret and MusicXML. It further contrasts with add_notes/add_rest by explaining they do not chain, so an agent can tell this tool apart from its closest siblings.

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 says this is the tool to reach for whenever more than a single beat is needed, and why add_notes/add_rest are unsuitable. It also gives a decision rule between caret and musicxml, including limitations (key/time signatures) and side effects (new flow), plus prerequisites like switch_mode and score_schema.

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/dorico-maestro'

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