Skip to main content
Glama
Sign In
mcp-score

mcp-score

by tskovlund
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_live_dynamic

Add dynamic markings like pp, f, or sfz to any measure in a live score, with optional staff selection for precise control.

Instructions

Add a dynamic marking to a measure in the live score.

Args: measure: Measure number (1-indexed). dynamic: Dynamic such as "pp", "p", "mp", "mf", "f", "ff", "sfz". staff: Staff index (0-indexed, default: 0).

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": {
      "measure": "<measure>",
      "dynamic": "<dynamic>"
    },
    "name": "add_live_dynamic"
  }
}

Input Schema

NameRequiredDescriptionDefault
staffNo
dynamicYes
measureYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It clearly states the mutation ('Add') and the target, but it does not disclose whether existing dynamics are replaced, how invalid measures are handled, or whether undo is supported. It is not misleading, but it is sparse.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and structured with numbered Args. Every sentence adds information, and the parameter explanations are exactly long enough.

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?

The description is sufficient for a simple add operation, especially with an output schema present. However, given no annotations and no behavioral caveats, it leaves a few gaps around failure modes and side effects that a more complete description could cover.

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

Parameters4/5

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

Schema description coverage is 0%, but the description adds meaningful parameter details: measure is 1-indexed, dynamic has a list of examples, and staff is 0-indexed with a default. This goes beyond the bare schema and helps the agent use the parameters correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Add a dynamic marking') on a specific resource ('a measure in the live score'). It is clearly distinct from sibling tools like add_live_note or add_live_rehearsal_mark.

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 implied by the operation's nature: it is the tool to add dynamics, while siblings handle other live-score annotations. However, there is no explicit guidance about when to prefer this tool over alternatives or any exclusions.

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