Skip to main content
Glama
Sign In
Dorico MCP Server

Dorico MCP Server

by happycastle114
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_score

Export a score to PDF for sharing or to MusicXML for interchange with other notation software.

Instructions

Export the score to PDF or MusicXML.

Args: path: Export file path format: Export format ("pdf" or "musicxml")

Returns: Success status and export path

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": {
      "path": "<path>"
    },
    "name": "export_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
formatNopdf

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It indicates the tool exports to a file and returns success status and path, which is transparent for a simple export. No contradictions, but could mention file overwrite behavior.

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?

Exceptionally concise with only two sentences and two argument lines. Every sentence earns its place, and the structure is front-loaded with the main purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity and presence of an output schema (implied), the description covers the essentials. Could mention that it exports the current score, but that may be inferred.

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 description adds meaning to both parameters beyond the schema: it explains 'path' as file path and 'format' with allowed values. Since schema coverage is 0%, this is valuable, though an enum for format would be even clearer.

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 clearly states the action (export) and the resource (score) along with the target formats (PDF or MusicXML), which is specific and distinguishes it from siblings like save_score.

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?

The description implies when to use (when you need PDF or MusicXML output) but does not explicitly state alternatives or when not to use. Sibling tools like save_score suggest a difference, but no guidance is provided.

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

Deploy Server

Other Tools