Skip to main content
Glama
MuseScore MCP Server

MuseScore MCP Server

by ghchen99

Get Style

get_style

Read MuseScore style settings by internal key, returning current values and listing any keys MuseScore does not recognize.

Instructions

Read score style settings (Format → Style) by MuseScore's internal key, e.g. "createMultiMeasureRests", "chordSymbolAFontSize", "minMeasureWidth". Returns the current values, and lists under "unknown" the keys MuseScore does not have.

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": {
      "keys": "<keys>"
    },
    "name": "get_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYesStyle keys to read

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose genuinely useful behavior beyond the schema: current values are returned and unrecognized keys are grouped under "unknown" rather than erroring. It omits connection/auth requirements and whether partial failures affect the result shape.

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?

Two tight clauses, the read action front-loaded, examples inline, and the unknown-key behavior in the final clause. Nothing is redundant.

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

Completeness4/5

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

An output schema exists, so return values need not be spelled out, and the input is a single well-documented array. The description plus schema is nearly sufficient; only environment prerequisites are unaddressed.

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 coverage is 100% for the single `keys` parameter, so baseline is 3. The description does add meaning by showing the key naming convention (camelCase internal identifiers like "chordSymbolAFontSize"), which helps an agent construct valid values rather than guess.

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?

"Read score style settings (Format → Style) by MuseScore's internal key" gives a specific verb (read) and resource (style settings), plus three concrete example keys. The read verb implicitly separates it from set_style, but it never names the write counterpart explicitly.

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?

The examples and the parenthetical UI path make the intended use clear by implication, and "Read" signals it is not for changes. However, there is no explicit guidance on when to prefer this over get_score, no statement that writes belong in set_style, and no mention of prerequisites such as an active MuseScore connection.

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