mcp-score

Overview Schema Source Related Servers Discussions Admin

set_live_time_signature

Change the time signature from a specified measure onward in the active score. Provide the measure number, beats per measure, and beat unit to update the notation.

Instructions

Set the time signature from a measure onward in the live score.

Args: measure: Measure number (1-indexed). numerator: Beats per measure (e.g. 3 in 3/4). denominator: Beat unit (e.g. 4 in 3/4).

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>",
      "numerator": "<numerator>",
      "denominator": "<denominator>"
    },
    "name": "set_live_time_signature"
  }
}

Input Schema

Name	Required	Description	Default
`measure`	Yes
`numerator`	Yes
`denominator`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 26, 2026

TDQS

A4/5.0

Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only states the basic action without mentioning side effects (e.g., whether existing signatures are overwritten), prerequisites (e.g., requiring a live connection), or reversibility. This is insufficient for a mutation tool.

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 a single-purpose sentence followed by a brief parameter list. It is front-loaded with the core action and remains compact with zero 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?

The description fully covers the parameters but omits operational context: it does not mention that the tool likely requires an active connection (given sibling connect tools) or what happens to the existing time signature after the measure. An output schema exists, so return values are not required, but the missing context affects effective usage.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate, and it does. Each parameter (measure, numerator, denominator) is explicitly defined with a concrete example (3/4). This adds substantial meaning beyond the schema's plain titles.

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 ('Set the time signature'), a specific resource ('live score'), and the scope ('from a measure onward'). This clearly distinguishes it from sibling tools like set_live_key_signature and set_live_tempo.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description clearly indicates this is for changing time signatures in a live score, which implies when it should be used. It does not explicitly exclude alternatives or name conditions, but the context is unambiguous given the sibling set of musical element setters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.