Skip to main content
Glama

List Editions of a Work

list_editions
Read-onlyIdempotent

Every edition of one work that the library holds — the other witnesses to the same text, across languages and centuries. Give it a book_id (easiest: the id of any edition you already found) or a work_id. USE THIS when a quotation needs checking against more than one witness, when you want the original-language text behind a translation, or when comparing how a passage reads across editions — differences between witnesses are often the finding. Returns language, date, page count and translation coverage per edition, so you can pick the right one to read. Note: for multi-volume collected works the identifier names the SET rather than a single text, and the response says so explicitly when that applies.

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

Input Schema

NameRequiredDescriptionDefault
book_idNoAny edition you already have, by id or by the slug from its URL. Its work is looked up and the siblings returned.
work_idNoA work identifier, if you already have one (from get_book).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / book_id / description
      Previous value: -"Any edition you already have. Its work is looked up and the siblings returned."New value: +"Any edition you already have, by id or by the slug from its URL. Its work is looked up and the siblings returned."
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already cover readOnly, idempotent, non-destructive and closed-world behavior, so the description only needs to add context, and it does so well. It discloses the return payload's fields (language, date, page count, translation coverage) and flags the important edge case that a multi-volume collected work's identifier names the SET, with the response saying so explicitly. Permissions and rate-limit behavior are not covered, but that is a minor 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?

The definition is front-loaded with the resource definition, then the use cases, then the return description, then the caveat: a logical order with no wasted sentences. The phrase 'across languages and centuries' is colorful but still carries meaning, so the description earns its length despite being on the long side for this tool.

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?

There is no output schema, so the description must describe return values, and it does: it lists the per-edition fields and explains how to choose among them. The handling of the multi-volume edge case shows real diligence. Only the absence of any guidance on multiplicity or pagination keeps it from a full 5.

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 both parameters are already documented, and that sets the baseline at 3. The description adds only a little: it suggests 'the id of any edition you already found' as the easiest input and implies that book_id and work_id are two routes to the same resolution. It adds no format or tie-breaking detail beyond the schema.

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?

The description names a specific verb and resource: 'Every edition of one work that the library holds,' and defines the scope with 'the other witnesses to the same text, across languages and centuries.' It is clearly distinguishable from search tools conceptually, but it never names a sibling such as search_translations, so it stops short of full sibling differentiation.

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?

It gives explicit 'USE THIS when...' triggers: checking a quotation against multiple witnesses, finding the original-language text behind a translation, and comparing how a passage reads across editions. It provides no when-not guidance and names no alternative tool, which keeps it below a 5.

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.