Skip to main content
Glama
Sign In

GrooveSheet

by net.groovesheet
OverviewDiscussionsAdmin

Search GrooveSheet songs

search_songs
Read-onlyIdempotent

Search GrooveSheet's public library of AI-transcribed songs by title or artist.

Returns up to 10 songs per page with id, title, artist, the separated instruments, whether the song has sheet music / MIDI / stems, and the song page URL. Track-level flags only: call get_song for which specific parts are scored, since a song can have sheet music for one part and only MIDI for another.

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": {
      "query": "<query>"
    },
    "name": "search_songs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page (10 songs per page).
queryYesSong title and/or artist, e.g. 'Easy On Me Adele'.
formatNoOnly songs offering this format. 'sheet' = readable sheet music (MusicXML/PDF), 'midi' = MIDI transcription, 'stems' = isolated audio. With an instrument, 'sheet' and 'midi' are checked for that specific part.
instrumentNoOnly songs with this part: drums, piano, bass, guitar, vocals or other.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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, openWorld=false), so the description earns credit for adding non-annotation behavior: the 10-per-page return shape, the fields returned, and the important limitation that flags are track-level not part-level. It does not discuss rate limits, auth, or empty-result behavior.

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 sentences, front-loaded with purpose then return shape, with zero filler. The limitation and sibling routing are packed into a single compact clause.

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 annotations, a full input schema, and an output schema present, the description covers what it must: what is searched, what comes back, pagination size, and the routing to get_song. Only marginal details (empty results, page ceiling) are absent, and those live in the schema.

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 schema already documents query, page, format, and instrument, including enum meanings and the instrument/format interaction. The description's 'by title or artist' only restates the query parameter, so baseline 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?

Specific verb (Search) + resource (GrooveSheet's public library of AI-transcribed songs) + scope (by title or artist). It explicitly names the sibling get_song as the different tool for part-level detail, so an agent can distinguish the two without opening either schema.

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?

Explicitly routes the agent: 'call get_song for which specific parts are scored' because this tool returns track-level flags only. That is a clear alternative-with-condition. There is no explicit statement of when not to use search (e.g. for known song IDs), which keeps it short of a 5.

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

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