Skip to main content
Glama

Search the people

search_people
Read-onlyIdempotent

Find people on IMSLP by name, resolving spelling variations to canonical categories for reliable access to their works.

Instructions

Find the composers, editors, arrangers and performers of IMSLP by name. The library addresses a person by a category, written 'Category:Surname, Forename', and that is what list_person_works and get_person take. A name is written the library's own way, so searching finds it where guessing at the spelling does not. Some rows stand for another category rather than for a person: the library keeps a redirect for a name spelled differently, and 'redirect_to' names the category it leads to. Follow it rather than reading works under the redirect, which holds none. IMSLP publishes no count of what a search matched, so 'total' is always null. When you show a person 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 among the people 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?

Beyond the readOnly/idempotent annotations, the description discloses meaningful behaviors: redirects appear as rows and should be followed rather than used for works, 'total' is always null because IMSLP provides no count, and attribution to IMSLP is required when displaying results. This significantly helps the agent interpret results.

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 front-loaded with the core purpose and each subsequent sentence earns its place by explaining redirects, count behavior, downstream usage, or attribution. It is detailed without becoming wasteful.

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?

The description covers purpose, result interpretation, redirect handling, missing total counts, and how to use the result with sibling tools. With annotations indicating read-only behavior and an output schema present, nothing essential is missing for correct selection and invocation.

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 the baseline is 3, but the description adds useful query semantics: names use the library's own spelling, so searching is more reliable than guessing. It also explains the category format relevant to interpreting the query results, giving the agent a better mental model of what it is matching.

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 clearly identifies the resource (people/contributors in IMSLP) and the action (search by name), and distinguishes it from search_works by focusing on person-oriented entities. It also clarifies that results are categories like 'Category:Surname, Forename', which is essential for downstream use.

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?

The description explains why to use this search rather than guessing spellings, and tells the agent that the resulting category is what list_person_works and get_person consume. It does not explicitly contrast with search_works, but the context is clear enough for an agent to select the right 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