Skip to main content
Glama

Get a catalogue

get_catalog
Read-onlyIdempotent

One catalogue of a composer's works (Op., BWV, K., S., KK…) by slug: its chapters and its works in catalogue order, with key, date and difficulty ratings. Paged: 50 entries per page by default, at most 100. get_composer lists a composer's catalogues and their URLs (the slug is the last part).

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": {
      "slug": "<slug>"
    },
    "name": "get_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1.
slugYesThe catalogue's slug, as in https://klavierstuck.org/catalog/<slug>, e.g. "kk-chopin".
limitNoEntries per page: 50 by default, at most 100 (larger values are capped).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description adds real value beyond them by disclosing result shape (chapters plus works in catalogue order, with key/date/difficulty) and paging behavior, though it says nothing about missing-slug errors or ordering edge cases.

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?

Three tight sentences: what it returns, how paging behaves, and where the slug comes from. Front-loaded with the payload description and free of filler.

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?

There is no output schema, so the description carries the burden of describing returns and does so explicitly. Combined with paging defaults and slug sourcing, an agent has everything needed to call this three-parameter read tool correctly.

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 slug, page and limit are already documented, and the description's '50 by default, at most 100' largely restates the limit field. The one genuine addition is how to obtain the slug via get_composer, which makes the baseline 3 appropriate.

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 ('One catalogue of a composer's works ... by slug') and enumerates what it returns: chapters and works in catalogue order with key, date and difficulty ratings. The parenthetical catalogue-type list (Op., BWV, K., S., KK) disambiguates it from work-level siblings, and it is clearly distinct from get_composer.

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 concrete prerequisite guidance for the required slug by routing to get_composer and explaining the slug is the last URL segment. It does not state explicit when-not-to-use conditions versus get_work or search_works, so it stops short of full alternative routing.

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