ScanSing: sheet music to MusicXML

Count pages

inspect_score

Read-onlyIdempotent

The kind and page count of a file, without recognising it or charging pages. Use it to pick pages for a long PDF or to check the quota (get_usage) first. Calls the ScanSing API, see https://scansing.app/mcp/.

Input Schema

Name	Required	Description
`url`	No	http(s) URL of a PDF or image of sheet music
`path`	No	local file path; only when this server runs on the same machine (stdio)
`attachment`	No	a PDF or image the user attached to the chat (ChatGPT fills this in: download_url, file_name)
`file_base64`	No	the file itself, base64 (a data: URL is fine)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 4, 2026
- removedInput schema / $defs / Attachment / properties / file_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / $defs / Attachment / properties / file_id / default
```
Removed value: -null
```
- addedInput schema / $defs / Attachment / properties / file_id / type
```
Added value: +"string"
```
- removedInput schema / $defs / Attachment / properties / file_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- changedInput schema / $defs / Attachment / properties / file_name / default
```
Previous value: -nullNew value: +""
```
- addedInput schema / $defs / Attachment / properties / file_name / type
```
Added value: +"string"
```
- removedInput schema / $defs / Attachment / properties / mime_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- changedInput schema / $defs / Attachment / properties / mime_type / default
```
Previous value: -nullNew value: +""
```
- addedInput schema / $defs / Attachment / properties / mime_type / type
```
Added value: +"string"
```
- changedInput schema / $defs / Attachment / required
```
Previous value: -[
-  "download_url"
-]New value: +[
+  "download_url",
+  "file_id"
+]
```

Changed2 schema fields changedOct 4, 2026

addedInput schema / $defs

Added value: +{
+  "Attachment": {
+    "description": "A file the user attached in ChatGPT, as ChatGPT hands it to a tool.",
+    "properties": {
+      "download_url": {
+        "title": "Download Url",
+        "type": "string"
+      },
+      "file_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "File Id"
+      },
+      "file_name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "File Name"
+      },
+      "mime_type": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Mime Type"
+      }
+    },
+    "required": [
+      "download_url"
+    ],
+    "title": "Attachment",
+    "type": "object"
+  }
+}

addedInput schema / properties / attachment

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/Attachment"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "a PDF or image the user attached to the chat (ChatGPT fills this in: download_url, file_name)"
+}

First observedOct 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered; the description goes further by disclosing the economically important traits that annotations cannot express — no recognition is performed and no pages are charged. That is exactly the value-add expected. It does not mention rate limits or what an unsupported file type returns, preventing a 5.

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?

Three short, front-loaded sentences: capability first, usage second, provenance last. The API/docs sentence is mild boilerplate but does not obscure anything.

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?

With an output schema present, return values need no explanation, and the description covers the two things an agent otherwise could not infer — that it is free of page charges and that it should be used to size work before recognition. Adequate for a read-only inspection tool.

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%, with each of url, path, attachment and file_base64 already documented in the schema, so the baseline is 3. The description gives no additional guidance on choosing among the four input methods, which would have been the natural value-add.

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 specifically that it returns a file's kind and page count, and the clause 'without recognising it or charging pages' distinguishes it from recognize_sheet_music and the other export/recognition siblings. The phrasing is noun-first rather than verb-led, which slightly softens the action, but the effect is unmistakable.

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

Usage Guidelines4/5

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

Gives two concrete uses — choosing a `pages` value for a long PDF and checking quota first — and points to get_usage as the quota sibling. It lacks an explicit 'do not use this to actually transcribe; use recognize_sheet_music instead' exclusion, so it falls short of full alternative routing.

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?