Skip to main content
Glama
Sign In
doricomcp

doricomcp

by kulbiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_tuplet

Inserts a tuplet into a Dorico score with a given ratio, note value, and note-input syntax, overwriting existing notes at the selected voice or beat.

Instructions

A tuplet typed with Dorico's note input, overwriting what is there: ratio "3:2", "5:4"; unit = the tuplet's note value (e, q, s, h); notes in add_notes syntax with notated values, e.g. "C5:e D5 E5" or "Eb4+G4:q B4 D5". Accidentals are always explicit (C#5, Ab4); plain letters mean naturals.

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": {
      "ratio": "<ratio>",
      "unit": "<unit>",
      "notes": "<notes>",
      "voice": "<voice>"
    },
    "name": "add_tuplet"
  }
}

Input Schema

NameRequiredDescriptionDefault
barNo
posNo
beatNo0
flowNo
unitYes
notesYes
ratioYes
voiceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the important destructive trait ('overwriting what is there'), which is genuinely useful. It says nothing about permission/precondition requirements (e.g. whether the target bar or voice must exist), what happens on a bad ratio, or what the call returns.

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 mutation warning is front-loaded and the format examples are compact and immediately usable. Slightly dense semicolon-chained phrasing, but no sentence is filler.

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?

For an 8-parameter mutation tool with no annotations and no output schema, the definition covers the musical payload well but leaves the addressing parameters (bar, pos, beat, flow, voice) and the voice precondition undocumented. An agent has enough to construct a tuplet but not enough to place it confidently.

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% across 8 parameters, so the description must compensate. It does well for the three core params – ratio examples ('3:2', '5:4'), unit enumerations (e, q, s, h), and notated notes with explicit accidentals – but bar, pos, beat, flow, and voice receive no explanation at all, leaving half the surface opaque.

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 names a specific verb and resource – a tuplet entered via Dorico's note input – and the 'overwriting what is there' clause tells the agent this mutates existing content. It is not explicitly contrasted with the obvious sibling add_notes, but the tuplet-specific framing plus the shared 'add_notes syntax' reference makes the distinction inferable.

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 only implied: the agent learns this is for tuplets and that it overwrites, but not when to choose it over add_notes, whether the voice must already exist, or how bar/pos/beat interact with placement. With 4 required parameters and no guidance on which positional parameter to supply, an agent must guess.

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