ScanSing: sheet music to MusicXML

Export PDF or PNG

export_score

Read-onlyIdempotent

A short-lived link to the score engraved as sheet music to print or view: a PDF of every page, or PNG pages. Works on any recognition: the original, one from label_notes (its names are engraved under the notes), and optionally one part, transposed or labelled on the way. The score is laid out anew from the MusicXML, not drawn over the scan. Nothing is recognised again, no pages are charged.

Input Schema

Name	Required	Description	Default
`key`	No	target key, e.g. 'G', 'Bb', 'F#m', 'E minor'
`file`	No	collection mode only: which MusicXML of `files`, e.g. '003.musicxml'
`page`	No	png only: this page; without it, a ZIP of every page
`part`	No	only this part: id (P2), name (Alto) or number (2)
`paper`	No	paper size	A4
`scale`	No	size of the music in percent; smaller fits more on a page
`format`	No	pdf (every page in one file) or png	pdf
`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
`semitones`	No	semitones to move, e.g. -2 (a tone down), 5
`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"
+}

AddedOct 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds material facts: the returned link is short-lived, nothing is re-recognised, no pages are charged, and the layout is regenerated from MusicXML rather than overlaid on the scan. The only omission is how long 'short-lived' actually is.

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?

The most important fact — a short-lived link, PDF or PNG — is front-loaded, and each following clause carries information (engraving source, no re-recognition, no page charges). It is slightly rambling with awkward mid-sentence line breaks, but there is 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?

Eleven parameters, but only one required; the schema is fully documented and an output schema exists, so the description needn't restate fields or return shape. It supplies the essential context — cheap re-export from existing MusicXML, works on original or label_notes recognitions. Only the link lifetime and collection-mode ('file') usage are left implicit.

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?

With 100% schema description coverage the schema already explains every parameter, so baseline is 3. The prose adds real meaning only for a few: that labels of a label_notes recognition are engraved under the notes, and that part/transposition/labels can be applied 'on the way'. The other nine parameters (paper, scale, page, file, labels_key, semitones, format...) are left entirely to the schema.

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 opening states the concrete output (a short-lived link to a freshly engraved score) and enumerates the two formats: PDF of every page or PNG pages. It also clarifies the key differentiator from a scan-based export — 'laid out anew from the MusicXML, not drawn over the scan'. It never names the closest sibling (export_midi / get_download_link), so an agent must infer that separation itself.

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: 'Works on any recognition: the original, one from label_notes...' plus 'no pages are charged' hints this is the cheap, repeatable way to produce a viewable artefact. There is no explicit statement of when to prefer this over export_midi, get_download_link, transpose_score or label_notes, even though the 'transposed or labelled on the way' phrasing overlaps visibly with those siblings.

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?