Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add Tuplet

add_tuplet

Add a tuplet at the current cursor position in a MuseScore score, with configurable ratio and base duration, and optionally advance the cursor afterward.

Instructions

Add a tuplet at the current cursor position.

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": "add_tuplet"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratioNoTuplet ratio as {"numerator": int, "denominator": int} (e.g. {"numerator": 3, "denominator": 2} for a triplet)
durationNoBase duration as {"numerator": int, "denominator": int}
advance_cursor_after_actionNoWhether to move cursor to next position after adding tuplet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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, yet it discloses almost nothing: not whether the cursor advance is default behavior, whether an existing selection is consumed, whether existing notes are modified, or whether a MuseScore connection is required. Only the schema parameter advance_cursor_after_action hints at post-action behavior.

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. It is efficient, though its brevity reflects omitted content rather than disciplined compression.

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 three-parameter mutation tool with nested objects, no annotations, and no output schema, the definition does not say what gets inserted (placeholder notes? rest?), how ratio and duration combine, or what state is required. An agent could call it but cannot predict the result.

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 100%, including per-property descriptions for ratio, duration, and advance_cursor_after_action, so the schema does the semantic work. The description adds no additional meaning such as how ratio interacts with duration or valid ratio bounds, so the baseline 3 applies.

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 and resource plus a scope qualifier: 'Add a tuplet at the current cursor position.' An agent can tell it creates a tuplet rather than a note, rest, or tie, but the description never contrasts it with adjacent tools like add_note or add_rest.

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 prefer a tuplet over adding individual notes with altered durations, and no stated prerequisites (e.g., that a score must be open and the cursor positioned). The only usage hint is the implicit 'current cursor position'.

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