Skip to main content
Glama

Search the works

search_works
Read-onlyIdempotent

Search IMSLP's library by title, composer, or words on a page to locate a specific work and its associated composer for retrieval.

Instructions

Search the works of IMSLP by title, by composer, or by words printed on their pages. Each row names the page of a work, which is how get_work and list_work_files address it: a title is written 'Work (Composer)', and the row splits it into the work and the person it names. IMSLP publishes no count of what a search matched, so 'total' is always null; 'has_more' and 'next_offset' say whether the library held more rows and where to read on from. A snippet is words taken from the page around the match. The library writes its pages in wikitext, so a snippet sometimes shows the name of a file rather than a sentence, and some rows carry none at all. The library titles a work in the language its composer used, so 'Die Zauberflöte' and not 'The Magic Flute', 'Sinfonia' and not 'Symphony'. A title translated into another language finds nothing, or finds only the works written about it: rows that look thin for a famous work are a sign the work sits under its original title, not that the library lacks it. Searching for a person by name finds the works naming them; search_people finds the person. When you show a result to a user, credit IMSLP and link the page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to serve, from 1 to 50.
queryYesWhat to look for in the works of the library. Words are matched across the page, not only titles.
offsetNoRows to skip, using the 'next_offset' a previous answer named.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYes
notesYes
queryYesThe search as it reached the library.
totalYesAlways null: IMSLP publishes no count of what a search matched.
offsetYes
sourceYes
licenseYes
resultsYes
has_moreYesTrue when the library named an offset to continue from.
returnedYes
next_offsetYesThe offset to read on from, as the library named it. Null when it named none.
Behavior5/5

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

Annotations already indicate a safe read-only operation, and the description adds valuable behavior beyond that: 'total' is always null, snippets may show filenames or be absent, wikitext can affect results, and attribution to IMSLP is required. No contradictions with the annotations.

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 description is long but information-dense, front-loading the core purpose and then adding caveats that materially affect result interpretation. Each paragraph earns its place, though it could be trimmed slightly without losing meaning.

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?

For a search tool with an output schema, the description covers query semantics, title-language pitfalls, pagination fields, snippet behavior, the relationship to sibling tools, and attribution requirements. Nothing essential for correct invocation and interpretation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a baseline of 3 applies, but the description enriches query semantics by explaining that words are matched across the page, not only titles, and that titles are in the composer's original language. It also explains pagination through 'next_offset', adding meaning to the offset parameter beyond the schema's type and default.

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: 'Search the works of IMSLP by title, by composer, or by words printed on their pages.' It also differentiates from search_people by explaining that searching a person finds works naming them while 'search_people finds the person,' so an agent can distinguish it from its sibling.

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 usage context: searches by title, composer, or page text, and warns that translated titles find nothing, pointing users to the original title. It explicitly names the alternative for person lookups ('search_people finds the person'), telling the agent when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smeet666/mcp-imslp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server