Skip to main content
Glama

Get a work

get_work
Read-onlyIdempotent

Details of one keyboard work in the Klavierstuck catalogue, by its slug: composer, catalogue references (Op., BWV, K., S.…), key, composition and publication dates, duration, instrument, performing forces, sub-genres, era, difficulty ratings with their scale, child works in order (e.g. the pieces of a set) and external links (IMSLP, Wikipedia, recordings). Returns the klavierstuck.org URL and the data sources to cite.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe work's slug, as in https://klavierstuck.org/work/<slug>, e.g. "3-nocturnes-op-9-chopin".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world lookup, so the safety profile is covered. The description adds genuinely useful behavior detail -- the breadth of returned musical metadata, plus a citable URL and data sources. It says nothing about what happens with an unknown or malformed slug, which is the remaining behavioral gap.

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-loaded with the core verb, resource and key, then a dense enumeration of returned fields that earns its length because no output schema exists. It is one very long sentence with a heavy parenthetical list, which reads less cleanly than a short structured breakdown, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, describing the returned payload and citation obligation is exactly the missing piece, and it is covered thoroughly. The only shortfall is not pointing at the tool used to discover a slug, which an agent may need to call this 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% and the single slug parameter is fully documented there, including the URL pattern and an example. The description only restates 'by its slug', adding no format, normalization or lookup semantics beyond 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 pair: retrieve details of one keyboard work from the Klavierstuck catalogue, keyed by slug. It immediately signals the single-record scope, which separates it from list/search siblings without needing to name them.

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 by 'by its slug' and the example slug format, and the returned-field list hints at when this is the right lookup. However, there is no explicit guidance on how to obtain a slug (e.g. via search_works) or when to prefer a sibling such as get_catalog or get_composer.

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