Skip to main content
Glama
Sign In
EasyMuseMCP

EasyMuseMCP

by Ranger013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Export an existing score

musescore_render

Export MuseScore-openable scores (.mscz, .musicxml, .mid, .gp) to PDF, PNG, SVG, MSCZ, MIDI, MP3, or MusicXML, with optional single-page export for supported formats.

Instructions

Export any score MuseScore can open (.mscz, .musicxml, .mid, .gp, …) to other formats, optionally a single page.

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>"
    },
    "name": "musescore_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoExport just this page (pdf/png/svg/mscz).
inputYesAbsolute path to the score file.
styleNoAbsolute path to a MuseScore .mss style file.
outDirNoOutput directory. Default: <score dir>/out.
formatsNoDefault: ["pdf","png"].
resolutionNoDPI for png/svg. Default 130.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 disclosure burden. It does add a genuine behavioral fact — the breadth of accepted input formats — but omits where files land (only in the schema), whether existing outputs are overwritten, and what is returned, which matters for a tool that writes to disk.

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?

One sentence, front-loaded with the verb and scope, no filler. The parenthetical format list earns its place by telling the agent which inputs are accepted, though a brief clause on output location would have cost little.

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?

With no output schema, the description should say what the call returns (output file paths, a list of generated formats) since the schema only documents inputs. It is otherwise adequate for a file-export tool whose parameters are fully documented.

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 all six parameters already carry their own descriptions, defaults, and enum values. The description's only parameter-relevant content, 'optionally a single page', restates the schema's page field. Baseline 3 applies.

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?

States a specific verb (export/convert) and resource (a score MuseScore can open), and enumerates accepted input formats. It is clearly distinguishable from siblings like musescore_edit or musescore_compose, though it does not name them.

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 format list tells the agent this is a conversion step, and 'optionally a single page' hints at the page parameter. Nothing says when to prefer this over musescore_view or musescore_inspect, and no prerequisites (e.g., a valid MuseScore install) are mentioned.

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