Skip to main content
Glama
Dorico Maestro

Dorico Maestro

project_file

Destructive

Open, save as, close, or revert a Dorico project and report when the action completes, giving controlled file-level project management via MCP.

Instructions

Open, save as, close or revert a Dorico project, and report when it is done.

Returns:
    Result dictionary with the command, whether Dorico finished it, and for
    save_as the written file, for open the flows of the project now active.

Note:
    Measured in Dorico Elements 6.2.40: save_as writes without a dialog and the
    open project becomes the new file; close with an ``openScoreID`` closes
    without a dialog. Revert asks for confirmation in a dialog that a person must
    answer in Dorico, and afterwards the project has a new ``openScoreID``.
    After a close, Dorico answers queries with ``kNoScore`` until a person
    focuses another project window.

    Closing without saving and reverting discard work, so both need
    ``confirm=True``. Opening a native project file was seen in Dorico's log
    but not yet measured over the API.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "project_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoopen and save_as: absolute path of a .dorico file.
actionYesopen a project file, save under a new path, close, or revert to saved.
confirmNoTrue authorises a change that discards work or cannot be undone.
timeoutNoSeconds to wait for Dorico, including any dialog.
save_changesNoclose: save before closing. False discards unsaved changes.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.8

TDQS

A4.1/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: save_as writes without a dialog, close with an openScoreID closes without a dialog, revert requires human confirmation in Dorico, and post-close queries return kNoScore. It also warns that closing without saving and reverting discard work and require confirm=True.

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 first sentence is front-loaded and clear, and the note is structured into actionable behavioral details. It is somewhat verbose and repeats return-value information despite an output schema, but most sentences carry useful operational context.

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 destructive file-operation tool, the description covers the key modes, confirmation requirements, dialog behavior, return shape, and known limitations. Combined with full schema coverage and annotations, it gives an agent enough context to invoke the tool correctly.

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 already 100%, but the description adds meaningful semantics for confirm and the destructive actions that require it. It also clarifies save_as and open behavior in terms of the resulting file and active flows.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives specific verbs and resource: open, save as, close, or revert a Dorico project. It is clear what the tool does, though it does not explicitly distinguish itself from the sibling save tool or other project-related siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the listed actions, and the notes clarify confirmation requirements for destructive paths. However, there is no explicit when-to-use guidance versus alternatives such as save or read_open_score.

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