Dorico Maestro

Overview Schema Source Related Servers Discussions Admin

run_command

Dispatch any catalogued Dorico command by ID with optional parameters. Use when no dedicated tool exists and check registry status to confirm the command is verified.

Instructions

Dispatch any catalogued Dorico command by ID, with optional parameters.

The escape hatch, reaching the whole catalogued command set rather than the
handful of tools here. What it can send is bounded by the catalog.

Returns:
    Result dictionary with the command outcome and the catalog row status, which
    says how well that command is actually established.

Note:
    Read the registry_status in the answer before trusting the result: a row may
    be verified, reachable, unavailable, broken or untested, and only verified
    has been seen to work. Combined with kOK meaning acceptance rather than
    effect (docs/protocol.md), a clean return from an untested row is weak
    evidence. Check with get_status or by inspecting the score.

    Prefer a dedicated tool where one exists: write_score, transpose,
    switch_mode, playback and save all add validation or verification this does
    not. Use search_commands to find a command ID and what it takes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No	Query parameters for the command, whose names differ per command and are declared in the catalog rather than here. Add {'confirm': True} to authorise a command the catalog marks destructive. Without it such a command is refused.
`command_id`	Yes	The command to send, exactly as the catalog declares it, e.g. 'Edit.Undo'. Case and spelling are not corrected. Find one with search_commands or the dorico://commands resource.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.5Sep 8, 2026

changedInput schema / properties / params / description

Previous value: -"Query parameters for the command, whose names differ per command and are declared in the catalog rather than here. Add {'confirm': True} to authorise a command the catalog marks destructive; without it such a command is refused."New value: +"Query parameters for the command, whose names differ per command and are declared in the catalog rather than here. Add {'confirm': True} to authorise a command the catalog marks destructive. Without it such a command is refused."

Changed2 schema fields changedv0.1.2Sep 7, 2026

addedInput schema / properties / command_id / description

Added value: +"The command to send, exactly as the catalog declares it, e.g. 'Edit.Undo'. Case and spelling are not corrected. Find one with search_commands or the dorico://commands resource."

addedInput schema / properties / params / description

Added value: +"Query parameters for the command, whose names differ per command and are declared in the catalog rather than here. Add {'confirm': True} to authorise a command the catalog marks destructive; without it such a command is refused."

First observedv0.1.0Aug 11, 2026

TDQS

A5/5.0

Behavior5/5

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

The description goes well beyond the annotations: it explains registry_status semantics (verified, reachable, unavailable, broken, untested), cautions that kOK means acceptance rather than effect, and discloses the confirm flag requirement for destructive commands. It also warns that command_id is matched exactly with no case/spelling correction.

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 sentence earns its place. It is front-loaded with the core purpose, then organizes Return behavior and safety notes into clear sections. No fluff or repetition of schema fields; it packs high-density operational guidance.

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 an escape-hatch command dispatcher, the description covers command discovery, parameter semantics, destructive-command authorization, result trustworthiness, verification alternatives, and fallback logic. The presence of an output schema also relieves it of explaining return structure, and it still explains the key status field.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema coverage is 100%, the description adds crucial meaning: params are command-specific and declared in the catalog, {'confirm': True} authorizes destructive commands, and command_id must match the catalog exactly. This is exactly the kind of contextual parameter guidance an agent needs beyond the raw 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: 'Dispatch any catalogued Dorico command by ID, with optional parameters.' It clearly frames the tool as an escape hatch that reaches the entire catalogued command set, distinguishing it from the more specialized sibling 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?

Usage guidance is explicit and actionable: 'Prefer a dedicated tool where one exists: write_score, transpose, switch_mode, playback and save all add validation or verification this does not.' It also directs the agent to search_commands for finding command IDs and parameters, and explains when this tool is the appropriate fallback.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.