Skip to main content
Glama
romanstark

Dorico Maestro

search_commands

Read-onlyIdempotent

Locate Dorico commands by query, category, or status to get exact IDs, parameters, and documentation before running them. Filter by verified status for commands known to work.

Instructions

Search the Dorico command catalog by query, category, or status.

Entirely offline: the catalog ships with this server, so nothing is asked of
Dorico and it need not be running.

Returns:
    Result dictionary with the total number of matches, a count per status, and
    the matching commands with their IDs, parameters and documentation.

Note:
    This is how to find a command ID and what it takes before sending it with
    run_command, and how to see the status that tells you how far to trust it.
    Only 'verified' rows have been observed to work.

    Prefer a dedicated tool where one exists: much of what the catalog can reach
    is already covered by write_score, transpose, playback, save and the rest,
    with validation run_command does not perform.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMost entries to return. The answer still reports the total number of matches, so a truncated result says so.
queryNoSubstring matched case-insensitively against command IDs and their documentation. Empty matches everything, which with a limit is how to browse a category.
statusNoHow well established the command is: 'verified', 'reachable', 'unavailable', 'broken' or 'untested'. Filter on 'verified' for the ones actually seen to work. Omit for every status.
categoryNoCommand family to restrict to, e.g. 'NoteInput', 'Edit' or 'Play', matched case-insensitively. Omit for every family.

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.2
    • addedInput schema / properties / category / description
      Added value: +"Command family to restrict to, e.g. 'NoteInput', 'Edit' or 'Play', matched case-insensitively. Omit for every family."
    • addedInput schema / properties / limit / description
      Added value: +"Most entries to return. The answer still reports the total number of matches, so a truncated result says so."
    • addedInput schema / properties / query / description
      Added value: +"Substring matched case-insensitively against command IDs and their documentation. Empty matches everything, which with a limit is how to browse a category."
    • addedInput schema / properties / status / description
      Added value: +"How well established the command is: 'verified', 'reachable', 'unavailable', 'broken' or 'untested'. Filter on 'verified' for the ones actually seen to work. Omit for every status."
  2. Addedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful context beyond those annotations: the search is entirely offline, Dorico need not be running, and the return shape includes total matches, per-status counts, and matching commands. This gives the agent a clear model of side effects and environment requirements.

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 offline behavior, return value, and usage guidance. Every sentence adds value: the offline note prevents false assumptions about needing Dorico, the return description clarifies output semantics, and the 'prefer a dedicated tool' line prevents misuse. It is longer than a one-liner but not bloated.

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?

The description is complete for a search tool of this complexity. It explains the environment constraint, the return value, the trust model for status, and the relationship to run_command and sibling tools. The input schema covers parameter semantics, and the output schema is present, so the description does not need to repeat structured details.

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?

Schema coverage is 100%, so the schema already documents all four parameters well. The description adds extra meaning by explaining that status indicates how far to trust a command and that only 'verified' rows have been observed to work, which directly informs how an agent should use the status parameter. It also reinforces that an empty query with a limit is a way to browse categories, matching the schema's description.

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: 'Search the Dorico command catalog by query, category, or status.' It clearly distinguishes this tool from siblings by explaining its role as the lookup mechanism for command IDs before using run_command, rather than a command-execution or music-editing tool.

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 guidance on when to use this tool: to find a command ID, understand its required inputs, and check status trust before invoking run_command. It also explicitly warns to prefer dedicated sibling tools where they exist, naming write_score, transpose, playback, and save as alternatives, which is strong routing guidance.

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