Steiner hat gesagt

List volumes

list_works

Read-only

Catalogue of all volumes in the Gesamtausgabe with title, section and whether the full text is available. Filter by title words, section and the year lectures were held. The reply text begins with the fixed phrase "Steiner hat gesagt:".

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": "list_works"
  }
}

Input Schema

Name	Required	Description
`year`	No	Volumes with lectures held in this year
`limit`	No
`title`	No	Words that must appear in the title (German)
`offset`	No
`section`	No	e.g. Schriften, Vorträge, Landwirtschaft, Medizin
`has_text`	No	Only volumes with (true) or without (false) full text

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add genuine behavioral context beyond that: the fields returned and the unusual fixed response prefix 'Steiner hat gesagt:', which an agent would otherwise misread. It says nothing about pagination or default result size for a 6-parameter listing tool.

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?

Two sentences, no waste: the resource and returned fields come first, then the filter capability, then the response-format quirk. Every sentence carries information an agent can act on.

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

Completeness3/5

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

With no output schema, the description helpfully names the returned fields and the response prefix, but omits pagination behavior and defaults, which matter for a 6-parameter listing tool capped at limit 500. Adequate but with a clear remaining gap.

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 67%, and the description adds meaning for the filters it covers: title words are matched against German titles, section is tied to the enumerated examples, year refers to when lectures were held, and full-text availability is filterable. Only limit and offset are left to the schema, which is acceptable at this coverage level.

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 concrete verb and resource ('Catalogue of all volumes in the Gesamtausgabe') and enumerates the returned fields (title, section, full-text availability). It is clearly a browse/list operation, distinguishable in spirit from get_work and read, though it never names a sibling 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?

The phrase 'Filter by title words, section and the year lectures were held' implies when the filters apply but gives no guidance on when to list versus using search or count_matches, and no note on prerequisites or result-size limits despite limit/offset parameters.

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

All Steiner hat gesagt tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?