Skip to main content
Glama
romanstark

Dorico Maestro

analyze_harmony

Read-onlyIdempotent

Identify the key of a score and name every chord in Roman numerals. Works offline on raw score data to provide a tonal center estimate and full harmonic analysis.

Instructions

Estimate the key of a ScoreSpec and name its chords in Roman numerals.

Entirely offline: the score is analysed as data and Dorico is not involved, so
this works on music that has never been in a project.

Returns:
    Result dictionary with the key estimate, its confidence, and a Roman numeral
    reading of each sonority.

Note:
    Key estimation relies on pitch distribution. For short or highly chromatic
    excerpts, verify the estimated tonal center before relying on Roman numerals.

    This answers what the harmony is. For whether the voices move well between
    those chords use check_voice_leading, for strict two-part exercises
    check_counterpoint, and for what could come next suggest_next_chord.

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.

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. Changed1 schema field changedv0.1.2
    • 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?

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral detail: the analysis is entirely offline and does not involve Dorico, the return value is a result dictionary with key estimate, confidence, and Roman numerals, and key estimation relies on pitch distribution with a caveat for short or chromatic excerpts. This goes well beyond what annotations convey.

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, then uses short labeled sections for returns and notes. Every sentence adds information: offline behavior, output contents, a limitation, and sibling routing. There is no filler or repetition of schema details.

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 single-parameter, read-only analysis tool with a rich output schema, the description is complete. It covers the operation, the execution context, the result shape, a known limitation, and alternatives. The agent has everything needed to decide when to call it and what to expect.

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% and there is only one parameter. The schema already explains the score parameter thoroughly as a ScoreSpec object and even points to score_schema for the exact shape. The description merely refers to 'ScoreSpec,' so it adds no new parameter meaning beyond the schema.

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 verb and resource: 'Estimate the key of a ScoreSpec and name its chords in Roman numerals.' This clearly identifies the operation, the input, and the output. It also positions the tool against siblings by saying 'This answers what the harmony is,' which helps distinguish it from related analysis tools.

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 explicit when-to-use guidance: it answers what the harmony is, and it names the alternatives for related questions (check_voice_leading for voice movement, check_counterpoint for strict two-part writing, suggest_next_chord for what could come next). It also clarifies that the tool works offline and on music never in a project, giving clear context for when this tool is appropriate.

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