Skip to main content
Glama
romanstark

Dorico Maestro

read_open_score

Export the open score as MusicXML to a chosen folder, then read back the full contents. Get reliable bar count, key, time signature, and pickup bar information.

Instructions

Read the whole open score back by way of a MusicXML export.

The only route to the full contents of the score that is open. Reads over the
Remote API see the selection alone, so everything else here works blind. This
is what makes bar count, key, time signature and above all a pickup bar
knowable instead of guessed.

Returns:
    Result dictionary with the parsed summary, the pickup finding, the last
    bar number, and the file that was read.

Note:
    Dorico's MusicXML export filter opens a modal dialog that requires user
    confirmation. This tool triggers the export dialog and awaits the resulting
    file in export_dir. Point the export dialog to export_dir once in Dorico to
    enable one-key export confirmations on subsequent reads.

    The result is a snapshot of the score at export time. Re-export after
    edits to refresh score state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
triggerNoTrue opens Dorico's MusicXML export dialog first. False skips that and reads whatever MusicXML already lies in the folder, which is what to use after a timeout or a manual export.
export_dirYesFolder Dorico's export dialog is pointed at. The newest MusicXML file that appears there is the one read back.
wait_secondsNoHow long to wait for the file while a person confirms the dialog. The call returns as soon as one appears.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Addedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that Dorico opens a modal confirmation dialog, that the tool triggers an export and waits for a file, and that the result is a snapshot which may be stale after edits. This is important behavioral context the agent would otherwise have no way to know.

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 front-loaded with the core purpose, followed by a clear returns section and a focused note. Every sentence earns its place, and the modal-dialog caveat is appropriately separated from the main purpose.

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?

Covers what the tool does, why it matters, what it returns, how the dialog interaction works, and how stale results should be handled. With a detailed input schema and output schema present, nothing an agent needs to call this correctly 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 coverage is 100%, so the baseline is 3. The description mostly reinforces the schema's parameter meanings rather than adding new parameter-specific detail, though the note about the export dialog and one-key setup does enrich the context around `export_dir` and `trigger`.

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?

States a specific verb and resource: 'Read the whole open score back by way of a MusicXML export.' It also distinguishes itself from selection-scoped reads by explaining that Remote API reads see only the selection, making this the only route to the full score contents.

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 positions the tool as the only way to access full-score contents, contrasting with selection-only reads. It also advises when to refresh the snapshot after edits, and the trigger parameter description gives a clear condition for when to use False after a timeout or manual export.

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