Skip to main content
Glama
Sign In
doricomcp

doricomcp

by kulbiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_grace_note

Add a grace note before an existing note at a specified bar, beat, and voice. Use it to insert ornamental notes into a Dorico score at a chosen pitch.

Instructions

Add a grace note before the note at the given position (value: notated length, default quaver).

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": {
      "pitch": "<pitch>",
      "voice": "<voice>"
    },
    "name": "add_grace_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
barNo
posNo
beatNo0
flowNo
pitchYes
valueNoe
voiceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/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 conveys that this is an insertion (not an append) and defines the value semantics, but says nothing about permissions, what happens on an empty position, whether the grace note can be removed, 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?

A single front-loaded sentence with no filler, and the one clarifying detail (value semantics) is attached to the relevant term. However, its brevity leaves no room for the positional context an agent needs to actually form the call.

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

Completeness2/5

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

For a 7-parameter mutation tool with no annotations, no output schema, and no schema descriptions, the definition is far too thin — it leaves the agent unable to determine how bar/pos/beat/flow combine to identify the insertion point.

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

Parameters2/5

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

With 7 parameters and 0% schema description coverage, the description only clarifies 'value' (notated length, default quaver) and partially 'pos'. The meaning of bar, beat, flow, pitch, and voice — including how they interact to locate the target note — is left entirely undocumented.

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?

States a specific verb ('Add') and resource ('grace note') plus the insertion point ('before the note at the given position'), which distinguishes it from siblings like add_notes and add_articulation. It never names a sibling alternative, but the operation 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 Guidelines2/5

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

The phrase 'before the note at the given position' implies an existing target note is required, but there is no explicit when-to-use guidance, no mention of prerequisites or failure behavior when no note exists at that position, and no routing to related tools.

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