Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Restore Backup

restore_backup

Restore a score version saved before an apply_measure_repeats edit and reload it in MuseScore, backing up the current version first. Defaults to the newest backup.

Instructions

Bring back the version of the open score saved before an apply_measure_repeats edit (the newest backup by default) and reload it in MuseScore. The current version is backed up first.

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

Input Schema

NameRequiredDescriptionDefault
backupNoBackup file to restore. Defaults to the newest backup of this score.
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/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose real behavior: it is a mutating operation, the current version is backed up before overwrite (making the change effectively recoverable), and the score is reloaded in MuseScore. It omits prerequisites (whether a live MuseScore connection is required) and failure behavior when no backup is available, which keeps it short of a 5.

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?

A single front-loaded sentence covering the action, the scope, the default, and the safety side effect, with no filler. Every clause earns its place.

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 two-optional-parameter mutation tool with no output schema or annotations, the description covers what is restored, what happens to the current state, and where the result appears. Only the connection prerequisite and behavior when no backup exists are left unstated.

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%, so the baseline is 3. The description's only parameter-adjacent information — that the newest backup is used by default — restates what the schema already declares for 'backup', and it adds nothing beyond the schema for 'score_path'.

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 uses a specific verb ('bring back') plus a specific resource (the score version saved before an apply_measure_repeats edit) and adds the side effect of reloading it in MuseScore. Naming apply_measure_repeats as the counterpart operation lets an agent distinguish this restore path from the edit path without opening any schema.

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 only implied: the agent can infer this is the recovery path after a bad apply_measure_repeats edit, and the 'newest backup by default' note tells it which backup is chosen when unspecified. There is no explicit when-to-use/when-not statement, no mention of what to do if no backup exists, and no named alternative for other recovery needs.

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