Skip to main content
Glama

Browse a category

browse_category
Read-onlyIdempotent

List the works IMSLP files under one category, such as a genre, key, instrumentation or period. Pass a category name exactly as the library writes it, since unknown names return the same as empty ones.

Instructions

Read the works IMSLP files under a category: a genre, a key, an instrumentation or a period. The library writes these names itself, and get_work hands them back for a work under 'genre_categories': 'Nocturnes', 'For piano', 'Scores featuring the piano', 'B-flat minor'. Pass one of those rather than a name of your own, since a category the library does not hold answers exactly as an empty one does. The 'Category:' prefix may be left out. The library cannot cross two categories, so a question naming both a genre and an instrument is answered by browsing one and reading the other off each work. IMSLP publishes no count of what a category holds, so 'total' is always null; 'has_more' and 'cursor' say whether more rows remain and how to read them. When you show a work to a user, credit IMSLP and link the page.

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": {
      "category": "<category>"
    },
    "name": "browse_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to serve, from 1 to 100.
cursorNoThe 'cursor' a previous answer named, to read on from where it stopped. The library writes it itself, so it is passed back as it was given rather than built.
categoryYesThe category to read, in the library's own wording, for example 'For piano', 'Nocturnes' or 'Category:B-flat minor'. The prefix is added when it is left out.

Output Schema

NameRequiredDescriptionDefault
limitYes
notesYes
totalYesAlways null: IMSLP publishes no count of what a category holds.
cursorYesThe cursor to read on from, as the library named it. Null when it named none.
sourceYes
licenseYes
resultsYes
categoryYesThe category as it reached the library, prefix included.
has_moreYesTrue when the library named a cursor to continue from.
returnedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.0
    • removedOutput schema / properties / cursor / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / cursor / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / results / items / properties / composer / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / composer / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent and open-world, yet the description adds non-obvious traits: an unheld category answers identically to an empty one (a silent failure mode), 'total' is always null because IMSLP publishes no counts, and 'has_more'/'cursor' carry the continuation state. Also flags the attribution/link obligation when presenting a work.

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 core action and the source of valid values before the caveats, and every sentence carries information. It runs slightly long, with the pagination and attribution notes packed into the middle and end rather than separated.

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?

Covers the mutation-free read model, the silent-empty pitfall, pagination contract, and the cross-category limitation. With an output schema present it need not describe return shapes, yet it explains the one field ('total') whose null value would otherwise confuse an agent.

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 real meaning: 'category' must be the library's own wording with examples drawn from 'genre_categories', and the prefix rule. The warning that an invalid category silently mimics an empty one is a semantic sharpening not present in the schema.

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 ('Read the works IMSLP files under a category') and immediately enumerates the four category kinds (genre, key, instrumentation, period) with concrete examples. An agent can distinguish this from get_work, which is named explicitly as the place category names come from.

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?

Gives clear operating conditions: pass the library's own category wording rather than inventing one, the 'Category:' prefix is optional, and two-facet questions must be answered by browsing one facet and reading the other off each work. It does not name search_works as the alternative for free-text queries, which is the one routing gap.

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