Skip to main content
Glama
Sign In
doricomcp

doricomcp

by kulbiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

edit_notes

Modify selected notes in a live Dorico score by applying pitch, duration, tie, respell, delete, or rest-removal actions for precise score corrections.

Instructions

Apply an edit to notes: pitch_up/pitch_down (diatonic steps x count), chromatic_up/down, octave_up/down, respell_above/below, double_duration, halve_duration, tie (to the next note of the same pitch), delete; remove_rests on rest ids (Dorico's Remove Rests: the voice shows a gap there, e.g. a divisi line that pauses).

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": {
      "event_ids": "<event_ids>",
      "action": "<action>"
    },
    "name": "edit_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowNo
countNo
actionYes
event_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it never says whether these edits are destructive, undoable, or what happens to unselected notes/voicing when a chord member is transposed or deleted. It does add real behavioral detail for tie ("to the next note of the same pitch") and for remove_rests (a gap appears in the voice), which shows the description could have disclosed more but stopped short.

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 dense action list is front-loaded and each item earns its place as the only available enumeration of valid action values. The sentence is long and multi-clause, but trimming it would lose semantic content rather than noise.

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?

No output schema and no annotations mean everything must come from the description, which covers action semantics well but leaves the flow parameter and the event_ids/rest-id disambiguation unaddressed. It is adequate to invoke correctly for the documented actions, but not complete for a four-parameter mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the action string has no enum, so the enumerated action values are genuinely valuable added meaning; "diatonic steps x count" also indirectly documents the count parameter. However, event_ids and flow receive no explanation, leaving a quarter of the parameters undocumented anywhere.

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 opens with a specific verb+resource ("Apply an edit to notes") and then enumerates the concrete edit operations, including pitch transposition, respelling, duration scaling, ties and deletion. It is clearly distinguishable from add_notes or delete_events at a glance, though it never explicitly contrasts itself with those siblings.

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?

There is no statement of when to choose this tool over delete_events, add_notes, or copy_range; the reader must infer that this is the general-purpose note mutation entry point. The one contextual hint is for remove_rests ("the voice shows a gap there, e.g. a divisi line that pauses"), which explains a specific action but is not routing guidance.

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