GrooveSheet

Create a GrooveSheet upload link

create_upload_link

Make a link where the signed-in user uploads a song for GrooveSheet to transcribe.

Give the returned url to the user and ask them to open it and upload their audio; you cannot upload it yourself. The link is valid for 24 hours. The upload starts a free preview; the full song is charged to the user's minutes only if they choose it on groovesheet.net. Follow up with get_upload_status.

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": {
      "task": "<task>"
    },
    "name": "create_upload_link"
  }
}

Input Schema

Name	Required	Description	Default
`task`	Yes	What to make from the user's song: 'drums' (drum sheet music, MIDI and stem), 'piano' (piano sheet music and MIDI), 'guitar' (guitar sheet music with a TAB staff, and MIDI), 'bass' (bass sheet music and MIDI), 'chords' (a chord chart from the full mix), 'stems' (every part separated as audio), 'drums_midi' or 'piano_midi' (MIDI only, for a DAW). Nothing else is offered for uploads.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint=false, idempotentHint=false); the description adds substantive context beyond that — 24-hour link validity, that the upload starts a free preview, and that minutes are only charged if the user opts in on groovesheet.net. It also discloses the human-in-the-loop constraint, which is unusual and valuable.

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?

Front-loads the purpose in the first sentence, then adds operational, billing, and follow-up details in short sentences. Slightly dense given four separate threads (url handoff, expiry, billing, follow-up), but every sentence carries distinct information.

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?

With an output schema present, return structure need not be explained, yet the description still names the `url` field and the 24-hour window. Combined with annotations covering safety and the schema covering the enum, an agent has everything needed to call and follow up 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 description coverage is 100% and the `task` enum is exhaustively documented in the schema, so the description needs to add nothing. However, the description never mentions the `task` parameter or how the chosen task affects the result, so it does not go beyond the schema baseline.

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?

States a specific verb and resource ('Make a link where the signed-in user uploads a song... to transcribe') and clarifies the scope of what it produces. It distinguishes itself from siblings by explicitly routing the agent to the follow-up tool get_upload_status.

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?

Gives explicit operating instructions: hand the returned `url` to the user, the agent 'cannot upload it yourself', and follow up with get_upload_status. This is effectively when-to-use guidance plus an actionable next step, leaving nothing to inference.

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

All GrooveSheet 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?