Skip to main content
Glama
romanstark

Dorico Maestro

export_pdf

Export a Dorico score to PDF without opening a dialog, writing the file next to the project. Choose to export the current layout or all layouts for printable output.

Instructions

Export the score to PDF unattended without opening a dialog.

Writes the file next to the .dorico project, named after the layout. This is the
unattended path. File.Export opens a modal dialog and is not usable from here.

Returns:
    Result dictionary reporting whether the command was accepted.

Note:
    Receiving kOK does not prove a file exists yet. Dorico runs commands on its
    UI thread, so a request sent while a modal dialog is open waits in the queue
    until the dialog closes. Tested against Dorico Elements 6.2.30. Check the
    expected path on disk rather than trusting the return.

    The all_layouts path is catalogued as untested, unlike the current-layout
    path which is verified, so treat a multi-layout export as unproven and check
    what actually landed. For an interchange format rather than a printable one,
    use export_musicxml.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
all_layoutsNoFalse exports the layout currently on screen through Print.ExportCurrentLayoutAsPDF. True exports every layout in the project through Print.ExportAllLayoutsAsPDF, which writes one file per layout.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / all_layouts / description
      Added value: +"False exports the layout currently on screen through Print.ExportCurrentLayoutAsPDF. True exports every layout in the project through Print.ExportAllLayoutsAsPDF, which writes one file per layout."
  2. Addedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Even with annotations present, the description adds substantial behavioral context: the file is written next to the .dorico project, kOK does not guarantee file existence, commands run on the UI thread and can queue behind modal dialogs, and the all_layouts path is untested. It also discloses the tested version. This goes far beyond the annotations.

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 moderately long but every sentence contributes: core purpose first, then side-effect location, alternative exclusion, return semantics, asynchronous caveat, version testing, and unverified-path warning. Nothing is redundant or filler.

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 tool with one optional boolean parameter and an output schema, the description covers purpose, side effects, failure modes, testing status, and routing to the sibling export_musicxml. An agent has everything needed to decide when to call it and what to verify afterward.

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 input schema already fully documents the single all_layouts parameter, including which underlying command each value triggers. The description adds valuable caveats about the all_layouts path being untested and the need to check the filesystem, which enriches the parameter's 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 states a specific verb and resource: 'Export the score to PDF unattended without opening a dialog.' It clearly distinguishes itself from File.Export and from export_musicxml by contrasting unattended PDF export with the modal dialog path and with interchange-format export.

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 explicitly explains when to use this tool: for unattended PDF export, not via File.Export, and not for interchange formats, which should use export_musicxml. It also warns that all_layouts is unverified, guiding the agent to prefer the verified current-layout path.

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