Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set Score Header

set_score_header

Set or clear title, subtitle, composer, lyricist, and part name in a MuseScore score header; omit a field to keep it unchanged.

Instructions

Tidy the title frame at the top of the score: title, subtitle, composer, lyricist and the part name shown top-left in part scores (a long part name such as 'Player | Kit | Drums' runs into the title). Leave a field out to keep it, pass an empty string to remove it. Edits the score file and reloads it (undo with restore_backup).

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

Input Schema

NameRequiredDescriptionDefault
titleNoTitle (e.g. the song name)
composerNoComposer / artist, shown top-right
lyricistNoLyricist, shown top-left under the part name
subtitleNoSubtitle (e.g. "Drum chart")
part_nameNoPart name shown top-left (e.g. "Drums"); "" removes it
score_pathNoPath of the score file. Defaults to the file of the score open in MuseScore.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose the key side effects: it edits the score file and triggers a reload, and it names the recovery path (restore_backup). It does not say whether the reload discards unsaved state or whether the score must first be open, which are the remaining risky unknowns for a mutating tool.

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?

Front-loads the purpose, then packs the operational rules into two compact sentences with no filler. The omit/empty-string rule is compressed into the same paragraph as the layout motivation, making it dense but still scannable.

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?

For a 6-parameter, all-optional mutation tool with no output schema and no annotations, it covers what is edited, how omission works, and how to recover. It leaves out preconditions (score open, unsaved changes) and return behavior, which keeps it from being fully self-sufficient.

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 coverage is already 100%, so the baseline is 3; the description goes beyond it by explaining the null-omit versus empty-string-remove contract, which the schema's 'default: null' does not make explicit. The only unsupported addition is the concrete 'Player | Kit | Drums' example rationale for the truncation problem.

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?

States a concrete verb (tidy/edit) and a well-scoped resource (the title frame: title, subtitle, composer, lyricist, part name), and enumerates exactly which fields are touched. An agent can distinguish it from set_song_structure or add_text without further inspection.

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?

Gives the decisive partial-update rule ('leave a field out to keep it, pass an empty string to remove it') which tells the agent how to use it safely, and points to restore_backup for rollback. It does not state explicit exclusions or when to prefer a different tool, so it stops short of full when/when-not guidance.

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