Skip to main content
Glama
Sign In
EasyMuseMCP

EasyMuseMCP

by Ranger013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Transpose a score

musescore_transpose

Transpose a score by a specified semitone count (positive to go up) and export the result to PDF, PNG, mscz, MIDI, or MusicXML for quick key changes.

Instructions

Transpose any score by a number of semitones (positive = up) and export the result.

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": {
      "input": "<input>",
      "semitones": "<semitones>"
    },
    "name": "musescore_transpose"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesAbsolute path to the score file.
outDirNoOutput directory.
formatsNoDefault ["mscz","pdf","png"].
semitonesYesSemitones to transpose, e.g. 2 or -3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 full burden. It does disclose two useful traits: direction convention (positive = up) and that the tool exports output rather than only mutating. It does not say whether the original file is modified, where output lands if outDir is omitted, or what happens on unsupported input.

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 with no filler; the scope (any score) and direction convention are packed in without redundancy. Nothing could be cut without losing meaning.

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

Completeness2/5

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

With no annotations and no output schema, the description should explain the export behavior: default formats, where files land without outDir, and whether the input is touched. None of that is present, leaving a mutation-plus-export tool under-specified despite a 4-parameter surface.

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 'positive = up' adds a small amount of direction semantics for `semitones` beyond the schema's 'e.g. 2 or -3', but says nothing about outDir or formats beyond what the schema already documents.

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?

The description names a specific verb (transpose) and resource (score) plus the exported artifact, so an agent can tell it apart from render/edit/compose siblings. It stops short of explicitly differentiating itself from musescore_render (which also produces output files), but the transposition intent is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over musescore_edit or musescore_render, no preconditions (e.g. input must be a supported score format), and no note about whether transposition is applied in place or as a new export. The agent is left to infer everything from the verb.

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