ScanSing: sheet music to MusicXML

Get MusicXML

get_musicxml

Read-onlyIdempotent

The MusicXML of an earlier recognition, a slice at a time (or saved to a local file). With labels, each note's name is written under it (see label_notes); no pages are charged.

Input Schema

Name	Required	Description
`labels`	No	write each note's name under it as a lyric line: letters (C♯, B♭), solfege-fixed (Do…Si, Do is always C), movable-do (Do is the tonic), degrees (1…7 of the scale, ♭3) or kalimba (the tines' numbers); default none
`offset`	No	character offset to start from
`save_to`	No	local path to write the whole MusicXML to (stdio only)
`max_chars`	No	characters to return
`labels_key`	No	with labels movable-do, degrees or kalimba: the key they count from, e.g. 'E minor'; default: read off the music
`recognition_id`	Yes	id returned by recognize_sheet_music, e.g. rec_…

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026

changedInput schema / properties / labels / description

Previous value: -"write each note's name under it as a lyric line: letters (C♯, B♭) or solfege-fixed (Do…Si, Do is always C); default none"New value: +"write each note's name under it as a lyric line: letters (C♯, B♭), solfege-fixed (Do…Si, Do is always C), movable-do (Do is the tonic), degrees (1…7 of the scale, ♭3) or kalimba (the tines' numbers); default none"

addedInput schema / properties / labels_key

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 20,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "with labels movable-do, degrees or kalimba: the key they count from, e.g. 'E minor'; default: read off the music",
+  "title": "Labels Key"
+}

Changed1 schema field changedOct 5, 2026

addedInput schema / properties / labels

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 40,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "write each note's name under it as a lyric line: letters (C♯, B♭) or solfege-fixed (Do…Si, Do is always C); default none",
+  "title": "Labels"
+}

First observedOct 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive safety. The description adds meaningful behavior beyond them: paged delivery ('a slice at a time'), an alternative local-file mode, and the non-obvious billing rule that labeling notes incurs no page charges — something no annotation or schema conveys.

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?

Two tight sentences with the resource front-loaded and the modal alternative and billing caveat in the same breath. No filler.

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?

An output schema exists, so return-shape explanation is unnecessary. The description covers slicing, the file-save variant, and cost behavior; it could note how to continue paging across slices, but the offset parameter in the schema carries that.

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; labels_key, save_to, max_chars, and offset are all documented there. The description only vaguely reinforces slicing and labels, adding little beyond what the schema already states.

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 and resource: retrieves MusicXML for an earlier recognition, delivered as a slice or written to a local file. It does not name a sibling it is explicitly distinct from (get_recognition, export_score), but the resource is concrete enough to disambiguate.

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?

'of an earlier recognition' implies a recognition must exist first, and the labels clause points to label_notes for that feature's semantics. Beyond that it gives no guidance on when to prefer this over get_recognition, inspect_score, or export_score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ScanSing: sheet music to MusicXML tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?