ScanSing: sheet music to MusicXML

Upload a local file

get_upload_link

A one-off URL to upload a local file to and have it recognised, for when the file is on the user's machine and this server is remote. Run the returned command in a shell on that machine (with the file's path in place of FILE): it uploads the file, waits for the recognition (seconds to minutes) and prints its summary with id. Then use get_musicxml, describe_score etc. with that id. The URL works once, within 15 minutes; for another file ask for another link. Not for a file attached to the chat: pass that to recognize_sheet_music as attachment.

Input Schema

Name	Required	Description
`mode`	No	merged (default) or collection (a songbook, one MusicXML per number)
`pages`	No	PDF pages to recognize, e.g. '3' or '3-5'
`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
`filename`	No	the file's name, e.g. '06.pdf'
`labels_key`	No	with labels movable-do, degrees or kalimba: the key they count from, e.g. 'E minor'; default: read off the music

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

A4.7/5.0

Behavior5/5

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

The annotations already mark this as non-read-only, non-idempotent, closed-world, and non-destructive. The description adds important operational details beyond that: the URL works once, expires in 15 minutes, the upload waits for recognition, and prints a summary containing `id`.

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?

The description is dense but appropriately sized for a multi-step remote upload workflow. It is front-loaded with the core purpose and then covers execution, timing, follow-up, and exclusions without waste.

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

Completeness5/5

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

Given an output schema and 100% schema coverage, the description need not explain return values. For a remote upload workflow with expiration and follow-up requirements, the definition supplies everything an agent needs to select and invoke it correctly.

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 coverage is 100%, so the schema already documents all five parameters. The description only references a FILE placeholder in the command and does not add meaning for `mode`, `pages`, `labels`, or `labels_key`, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (a one-off upload URL) and its purpose (uploading a local file so it is recognized on a remote server). It also distinguishes this from the sibling path for chat attachments: 'Not for a file attached to the chat: pass that to recognize_sheet_music as `attachment`.'

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: the file is on the user's machine and the server is remote. It also explains the exact workflow (run the returned `command` with the file path in place of FILE), what happens next, and which follow-up tools to use with the resulting `id`.

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?