Skip to main content
Glama
Sign In
Dorico MCP Server

Dorico MCP Server

by happycastle114
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

save_score

Save the currently open score. Specify a file path to save to a new location, or save without a path to overwrite the existing file.

Instructions

Save the current score.

Args: path: File path to save to. If None, saves to current location.

Returns: Success status

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. Only states 'Save' (mutation) and 'Returns: Success status' without details on overwriting, error behavior, or side effects. Minimal behavioral disclosure.

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?

Very concise, with one sentence plus Args/Returns. No wasted words. Could be slightly more structured (e.g., bullet points) but efficient for a simple tool.

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

Completeness3/5

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

Given a single optional parameter and output schema, the description covers basic usage but lacks details like file format, overwrite behavior, and return type specifics. Adequate but incomplete.

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 0%, but description adds meaning: 'path: File path to save to. If None, saves to current location.' This clarifies the parameter beyond the schema, though format or valid values are omitted.

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 clearly states 'Save the current score' with a specific verb and resource. It distinguishes from siblings like export_score (which implies different format) and open_score (which is reading), but does not explicitly differentiate.

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

Usage Guidelines2/5

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

No guidance on when to use vs alternatives. Does not mention use cases, prerequisites, or when not to use. Lacks any contextual advice.

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