Skip to main content
Glama
romanstark

Dorico Maestro

read_score

Read-onlyIdempotent

Read MusicXML files to extract pitches, notes, and structure measure by measure. Use bar filters for targeted sections, returning a structured dictionary for offline analysis.

Instructions

Read an existing MusicXML file measure by measure using music21.

Entirely offline and read-only. This is the way to see pitches, which Dorico
itself will not report over the Remote API.

Returns:
    Structured dictionary with the metadata, parts, measures and note events.

Note:
    Use the bars filter rather than reading everything when the question is
    local: a full read of a long score returns every note of every part.

    To see the music currently in Dorico, export it with export_musicxml first
    and read that. read_project_info reads a .dorico project wrapper instead,
    and read_selection reports the live selection without pitches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNoWhich bars to read, as a filter string: '8' for one, '8-12' for a range, '8,10,12' for a list. Bars are counted from 1. Omit to read the whole score, which on a long one is a lot of output.
pathYesFilesystem path to the MusicXML file to read.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / bars / description
      Added value: +"Which bars to read, as a filter string: '8' for one, '8-12' for a range, '8,10,12' for a list. Bars are counted from 1. Omit to read the whole score, which on a long one is a lot of output."
    • addedInput schema / properties / path / description
      Added value: +"Filesystem path to the MusicXML file to read."
  2. Addedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

The description reinforces the read-only and offline nature, consistent with the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false). No side effects are hidden; the return type is mentioned as a structured dictionary.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficient, with each sentence contributing either to purpose, usage guidance, or alternative comparisons. It is slightly verbose but not unnecessarily long.

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 output schema exists (not shown but indicated), the description provides sufficient context about return structure (dictionary), usage scenarios, and tool relationships, making it complete for an agent to decide when and how to use it.

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?

The schema already provides 100% coverage with descriptions for both parameters. The description adds a practical tip about using the bars filter to limit output, enhancing the schema without redundancy.

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 tool reads an existing MusicXML file using music21, and distinguishes itself from siblings like read_selection and read_project_info by specifying 'existing MusicXML file' and 'measure by measure'.

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?

Provides explicit guidance on when to use this tool: use the bars filter for local questions, export from Dorico first to see current music, and contrasts with read_project_info and read_selection, leaving no ambiguity about alternatives.

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