Skip to main content
Glama

Search the catalog

search_catalog
Read-onlyIdempotent

Search Cesure's catalog of free pieces by words of a title, a composer or both: a piece is found when each word is in one of them, a short joining word such as 'by' aside; the best matches come first, 20 a call (offset skips that many; when there are more, the answer's more gives the next offset); returns title, artist, licence and link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords of a title or a composer; empty lists the catalog.
offsetNoHow many pieces to skip, best matches first (default 0): the answer's more gives the next.
languageNoen (default), fr or es.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "How many pieces to skip, best matches first (default 0): the answer's more gives the next.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.8/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 closed-world, so the safety profile is covered. Beyond that the description adds genuinely useful behavior the annotations do not: best matches come first, 20 results per call, offset skips, and the response's 'more' field supplies the next offset — a complete pagination contract. The listed return fields (title, artist, licence, link) are largely redundant given an output schema exists.

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?

One dense but front-loaded sentence that leads with what is searched, then the match rule, then ordering and pagination. Every clause carries information, though the run-on colon-and-parenthesis structure and the redundant return-field list cost it a point on tightness.

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 three-parameter, zero-required, read-only search tool with an output schema, the description covers matching semantics, result ordering, page size, and the offset/'more' continuation loop — everything needed to drive it correctly without guessing. Return values are also named, which is extra rather than missing.

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 coverage is 100%, so the baseline applies; both query and offset are already documented in the schema. The description does add real meaning beyond the schema by explaining the AND-across-words matching rule and the stopword exception for 'by', but it does not touch the language parameter or clarify how accented/multi-word composer names are handled.

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 a specific verb and resource — 'search Cesure's catalog of free pieces' — and defines the match rule (every word must appear in the title or composer, joining words like 'by' ignored). An agent immediately knows this is a public-catalog discovery tool rather than a personal-library operation, though it never names a sibling such as list_my_scores or read_score to draw the boundary explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the description tells you the tool matches on title/composer words and that 'empty lists the catalog', which effectively conveys the broad-search case. There is no explicit when-not guidance and no routing to alternatives for structured lookups (e.g., opening a known score by id), leaving that inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources