Skip to main content
Glama

Get Book

get_book
Read-onlyIdempotent

READ PIPELINE step 1 — DISCOVER. START HERE for any named work or author. Returns the book's AI-generated summary, chapter list, edition metadata, first_translation (the site's First Translation badge: badge_shown, badge_label, claim confirmed|candidate|defeated|not_applicable, the note shown on the book page, any Translation Card sentence, and prior English translations listed; it is a researched claim that no earlier English translation was found, may be wrong for multi-work volumes, and is not proof, so hedge it and link the page), DOI, page counts, IIIF manifest, and the cover image (inline, so you and the user can see the book). LANGUAGE: language is what is printed on THIS EDITION's leaves, which is frequently not the language the work was written in. Where the record knows they differ the response also carries work_language and a translation_note, and text_role (original / period-translation / modern-translation / unclassified) says what kind of witness this is — read them before describing a passage as the author's own words, because an edition can be a translation of a translation (de Slane's 1863 French Muqaddimah, read in English, is English←French←Arabic). Absent work_language means the work's language is NOT RECORDED on this record. It is not a statement that the edition is in the work's own language (most records have never been checked; Risner's 1572 Latin Alhazen carries none, and the work is Arabic). Only text_role: "original" asserts that these are the author's own words in the author's language; text_role: "unclassified" means nobody has examined it, so do not infer the work's language from language, and do not conclude the library lacks a tradition because a language filter came back empty. Use list_editions to find an original-language witness. The summary is typically a multi-paragraph orientation covering the book's argument, structure, and significance — often answering the question without further searching. Then: get_book_text to read a chapter or page range (step 2), get_quote / get_quotes to lock specific pages with full citation apparatus (step 3). search_within_book locates passages inside this book. MULTI-WORK VOLUMES: where the scans carry running heads, contains_works lists the works the volume ACTUALLY holds with their page spans, taken from the heads the printer put on each leaf. Trust it over the title — collected-works titles routinely name works the volume does not contain, and the volume holding a work often does not name it. If contains_works is absent the scans have no heads to read; status "insufficient-heads" means it was examined and could not be decided. EDITIONS: editions says which languages this book can be READ in and how many pages each covers ({ en: 357 } on most books, { en: 357, es: 357 } where a localized edition exists). Pass a code as lang to get_quote, get_quotes, get_book_text or search_within_book to read that edition; without it you get English.

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": {
      "book_id": "<book_id>"
    },
    "name": "get_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYesThe book: its id, or the slug from a book URL (the part after /book/). Both work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / book_id / description
      Previous value: -"The book ID"New value: +"The book: its id, or the slug from a book URL (the part after /book/). Both work."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), but the description adds substantial non-structured behavior: the cover image is returned inline, the summary is typically multi-paragraph orientation, and first_translation fields are 'a researched claim... may be wrong for multi-work volumes, and is not proof, so hedge it and link the page.' It also discloses the absence semantics of `work_language`, `text_role: "unclassified"`, and `contains_works` status 'insufficient-heads' — uncommon but critical behavioral caveats an agent could not infer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with a clear step/verb header and uses caps labels (LANGUAGE:, MULTI-WORK VOLUMES:, EDITIONS:) to segment the wall of text, which helps. However, it runs roughly 500 words for a single-parameter read tool, with a long nested parenthetical about first_translation and dense 'de Slane's 1863 French Muqaddimah' digressions that impair scannability; some of the language-ontology detail would serve better in a shared convention rather than this one description.

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?

No output schema exists, yet the description enumerates the return payload (summary, chapter list, edition metadata, first_translation sub-fields, DOI, page counts, IIIF manifest, cover image) and explains the meaning of the less obvious fields. For a single-required-param, read-only tool with annotations, nothing an agent needs in order to call it and interpret the response is missing.

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?

There is only one parameter and schema description coverage is 100%, with the schema already stating 'its id, or the slug from a book URL (the part after /book/)'. The description adds no further meaning about `book_id`. Instead it discusses a `lang` argument — but that parameter belongs to get_quote, get_quotes, get_book_text and search_within_book, not to this tool, so it does not enrich this tool's own input 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?

The description states a specific verb and resource ('Returns the book's AI-generated summary, chapter list, edition metadata...') and explicitly positions itself as 'READ PIPELINE step 1 — DISCOVER. START HERE for any named work or author.' It distinguishes itself from siblings by naming the next pipeline steps (get_book_text = step 2, get_quote/get_quotes = step 3, search_within_book for in-book passages), so an agent can select it without opening another schema.

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?

Gives explicit entry conditions ('START HERE for any named work or author'), explicit alternatives with their triggers ('Use list_editions to find an original-language witness', 'get_book_text to read a chapter or page range', 'search_within_book locates passages inside this book'), and an exclusion warning ('do not conclude the library lacks a tradition because a `language` filter came back empty'). Routing is unambiguous.

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.