Skip to main content
Glama
romanstark

Dorico Maestro

export_musicxml

Destructive

Convert a ScoreSpec into a MusicXML file on disk without opening Dorico. Preserves key, time, clefs, dynamics, tempo, and returns the written path for later import.

Instructions

Write a ScoreSpec to a MusicXML file on disk, without Dorico.

Entirely offline: no connection is opened and Dorico need not be running. Key,
time signature, clefs, dynamics and tempo all survive the round trip, which is
what makes this the way to set the two signatures no popover will accept.

Returns:
    Result dictionary with the outcome and the path that was written.

Note:
    A specified path is overwritten without confirmation. Omit the path to
    write to a temporary file.

    To get the file into Dorico afterwards, import_musicxml opens it as a new
    flow, and write_score(method='musicxml') does both steps in one call. For a
    printable file rather than an interchange one, use export_pdf.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoWhere to write the .musicxml file. An existing file at this path is overwritten. Omit to write to a temporary file and take the path from the answer.
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.

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. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / path / description
      Added value: +"Where to write the .musicxml file. An existing file at this path is overwritten. Omit to write to a temporary file and take the path from the answer."
    • 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.7/5.0
Behavior5/5

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

The annotations already mark the tool as destructive, and the description reinforces this by stating that a specified path is overwritten without confirmation. It also adds valuable behavioral context beyond annotations: entirely offline, no connection opened, Dorico need not be running, and musical elements survive the round trip.

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 well-structured and front-loaded with the core purpose; the offline behavior, return value, overwrite warning, and alternative tools each have a clear and compact section. No sentence is wasted, and the formatting makes the key warning and routing advice easy to scan.

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?

Given the annotations and output schema, the description is complete enough for an agent to call the tool safely: it covers destructive behavior, path handling, offline operation, return result shape, and how to get the file back into Dorico or produce a printable output. Nothing critical is missing.

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?

Schema description coverage is 100%, so the schema already documents both path and score thoroughly. The description adds little new parameter-level meaning beyond restating that a specified path is overwritten and that omission writes to a temporary file, which the schema also states. Baseline 3 is appropriate.

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 opening sentence states a specific verb and resource: 'Write a ScoreSpec to a MusicXML file on disk, without Dorico.' It also distinguishes this from export_pdf and write_score by naming them as alternatives with different purposes, so the agent can tell the tools apart immediately.

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?

The description gives clear routing guidance: import_musicxml opens the file into Dorico later, write_score(method='musicxml') does both steps in one call, and export_pdf is for printable rather than interchange files. It also explains the offline/no-Dorico context, which is a strong signal for when this tool is the right choice.

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