Skip to main content
Glama

Get a composer

get_composer
Read-onlyIdempotent

One composer by slug: dates, portrait, catalogues (with chapters), stylistic movements with their work counts, and a summary of the works: counts by sub-genre and the top-level works (first 100) with their number of child works. Use search_works with the composer's name to page through every work.

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_composer"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe composer's slug, as in https://klavierstuck.org/composer/<slug>, e.g. "frederic-chopin".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish that this is a safe, idempotent read. The description adds meaningful behavioral context: what sections are returned, that works summary is limited to the first 100 top-level works, and that exhaustive paging requires search_works.

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?

Front-loads the core action, then compactly enumerates return contents, and closes with a practical pagination note. The density is justified by the lack of an output schema, and there is no 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 must explain return shape; it does so thoroughly, including nested catalogues and movement counts, plus the 100-work limit and paging alternative. Nothing critical is missing for correct selection.

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% and the slug parameter is documented with format and an example. The description only restates that lookup is by slug, adding no further parameter semantics.

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: fetch one composer by slug. Enumerates the returned sections (dates, portrait, catalogues, movements, work summary) and names search_works as the route for paginating all works, so it is distinguishable from siblings.

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?

Clearly establishes the single-composer lookup use case and explicitly directs the agent to search_works when it needs to page through every work. The alternative and the condition selecting it are both stated.

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