Skip to main content
Glama
Sign In
EasyMuseMCP

EasyMuseMCP

by Ranger013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Look at a rendered page

musescore_view

Render one page of a MuseScore score as a PNG image so you can visually inspect the engraving before export or editing.

Instructions

Render one page of a score to PNG and return it as an image so you can check the engraving yourself.

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_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based. Default 1.
inputYesAbsolute path to the score file.
resolutionNoDPI, default 110 — raise it only when you need detail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does carry the disclosure burden and does well on the essentials: it renders only one page and returns an actual image (multimodal output), which the agent needs to know. It is silent on whether a PNG is written to disk, whether the file must already be open, and on cost/latency for high DPI, which are meaningful gaps for an unannotated tool.

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 sentence with the action, scope, and output front-loaded; nothing is wasted and there is no filler.

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?

For a simple three-parameter tool with full schema coverage and no output schema, the description covers what it does and what it returns. It stops short of the operational context an agent would want — file-state prerequisites, disk side effects, and how this relates to musescore_render.

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 three parameters (page, input, resolution) are already documented in the schema. The description reinforces the single-page semantics of 'page' but adds no format or behavior detail beyond that, so the baseline of 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 (render), a specific resource and scope (one page of a score), and the output form (PNG returned as an image). It does not distinguish itself from the sibling musescore_render, so an agent must infer the difference between rendering one page for visual inspection and whatever musescore_render produces.

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 clause 'so you can check the engraving yourself' implies the use case: visual verification of layout/engraving. However, it never names an alternative (e.g. musescore_render or musescore_inspect) or says when not to use it, leaving the choice between the two render-flavored siblings to inference.

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