Skip to main content
Glama
Sign In
doricomcp

doricomcp

by kulbiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_span

Adds voice-specific slurs, hairpins, octave lines, and glissandi between notes in a Dorico score; supports multiple spans in one call.

Instructions

A line from one note to another in the same voice: slur, cresc, dim, messa_di_voce (hairpins), 8va, 8vb, 15ma, 15mb (octave lines), glissando. Only that voice gets it, even with other voices on the staff. spans: several [start_event_id, end_event_id] pairs in one call (slurs: one undo step), e.g. a slur over every pair of quavers. Hairpins end at the end of the end note; for exact positions use add_hairpin.

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": {
      "kind": "<kind>"
    },
    "name": "add_span"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowNo
kindYes
spansNo
end_event_idNo
start_event_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavioral traits: the span attaches only to the addressed voice even when other voices share the staff, batching slurs costs a single undo step, and hairpins terminate at the end of the end note. It does not describe return values, failure modes, or whether invalid event IDs error or no-op.

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?

Roughly five short lines, front-loaded with what the tool adds, then voice scoping, then batching, then the hairpin caveat. Some telegraphic jargon ('cresc, dim', 'quavers') assumes domain fluency, 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 a five-parameter mutation tool with no annotations and no output schema, the description covers the core semantics (kinds, voice targeting, batching, hairpin endpoint) well. The undocumented flow parameter and the missing return-value or error behavior keep it from being fully self-sufficient.

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 five parameters, so the description must compensate. It does well for kind (listing nine valid values not present in the schema) and spans (format '[start_event_id, end_event_id] pairs' plus batching behavior). It says nothing about the flow parameter or the standalone start_event_id/end_event_id pair, leaving those undocumented in both places.

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 concrete resource and enumerates the span kinds (slur, cresc/dim hairpins, messa_di_voce, 8va/8vb/15ma/15mb, glissando), and explicitly carves out add_hairpin for precise positioning. It is distinguishable from siblings like add_dynamic and add_articulation. The phrasing 'A line from one note to another' is slightly elliptical as an opening, but the intent is unambiguous.

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?

It gives one explicit routing rule ('for exact positions use add_hairpin') and explains the batch use case for spans ('a slur over every pair of quavers'). It does not say when to prefer add_span over add_dynamic or add_note_marking, nor what preconditions exist (same voice requirement is stated as a constraint, not a when-to-use rule). Guidance is implied more than prescribed.

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