Skip to main content
Glama

Get Quotes (batch)

get_quotes
Read-onlyIdempotent

READ PIPELINE step 3 — CITE, in batch. Get verbatim text + citation_link for SEVERAL pages of a single book in one round-trip, to assemble a multi-passage dossier. Specify either pages (an explicit array, e.g. [12, 40, 41]) or an inclusive from/to range. Max 25 pages per call. Each entry carries its own citation_link to present alongside the quote, and — on non-Latin-script pages that have one — a romanized layer to show between the original and the translation (AI apparatus, not a transcription). Every entry also carries text_source: translation normally, or ocr_original on a leaf that is already English, where the verbatim text is original and must be attributed as the source's own words rather than as a translation. One batch can mix both — a Latin volume can hold an English preface. Batch pages count toward the shared daily page budget (see get_book_text); this is a citation tool, and corpus-scale extraction belongs on the dataset API (sourcelibrary.org/dataset).

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd page (inclusive) of a range. Use with from.
fromNoStart page (inclusive) of a range. Use with to.
langNoISO code of the EDITION to quote, e.g. "es". Default "en". Resolved per page — one batch can mix editions, so read `quote.lang` on each entry rather than assuming the whole dossier is in one language.
pagesNoExplicit list of page numbers (e.g. [12, 40, 41]). Use this OR from/to.
book_idYesThe book: its id, or the slug from a book URL (the part after /book/). Both work.
include_imageNoAlso return page scans as inline images (display size). The first 5 pages of the batch get inline image blocks; every entry still carries its page_image_url in the JSON.

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. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "ISO code of the EDITION to quote, e.g. \"es\". Default \"en\". Resolved per page — one batch can mix editions, so read `quote.lang` on each entry rather than assuming the whole dossier is in one language.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / include_image
      Added value: +{
      +  "description": "Also return page scans as inline images (display size). The first 5 pages of the batch get inline image blocks; every entry still carries its page_image_url in the JSON.",
      +  "type": "boolean"
      +}
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial operational detail beyond them: a hard cap of 25 pages per call, consumption of a shared daily page budget, per-entry lang resolution across mixed editions, and the text_source/ocr_original attribution distinction. These are exactly the constraints an agent would otherwise get wrong.

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-loads the role ('READ PIPELINE step 3 — CITE, in batch') before the mechanical details, and each subsequent sentence carries a distinct constraint. It is dense and long, with some embedded parentheticals that could be tightened, but nothing is redundant.

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?

With no output schema, the description takes responsibility for describing the return shape (citation_link, romanized layer, text_source, page_image_url) and does so per entry. For a 6-parameter read tool with a page cap and a budget interaction, nothing essential is missing.

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 100%, so the baseline is 3, but the description adds real constraint knowledge: pages and from/to are mutually exclusive alternatives, the range is inclusive, and the 25-page cap and inline-image behavior (first 5 pages only, with page_image_url always present) are not visible in the schema. That is meaningful added meaning for the batch parameters.

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 (get verbatim text + citation_link for several pages of one book) and scopes it as batch citation assembly, which cleanly distinguishes it from single-quote and full-text siblings. The 'READ PIPELINE step 3' framing tells an agent exactly where this sits in the workflow.

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?

Explicitly says when to use it (assemble a multi-passage dossier in one round-trip) and when not to (corpus-scale extraction belongs on the dataset API), and points to get_book_text for the page-budget rule. It does not name a single-page alternative for one-off quotes, so the routing for that case is left implicit.

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.