Bibooks

Read an audiobook's text

read_book

Read-onlyIdempotent

Read a public audiobook's bilingual text: its sentence pairs (each original sentence with its translation, plus a Latin-script romanization for languages that have one), in reading order. Returns at most limit pairs starting at offset; continue with offset + limit while has_more is true. total_pairs is the book's length.

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

Input Schema

Name	Required	Description
`limit`	No	Maximum number of sentence pairs to return.
`offset`	No	Index of the first sentence pair to return.
`book_id`	Yes	The book's id (the `id` field of a Book).

Output Schema

Name	Required	Description
`limit`	Yes	Maximum number of pairs in this window.
`pairs`	Yes
`offset`	Yes	Index of the first pair in this window.
`book_id`	Yes
`has_more`	Yes	Whether pairs exist after this window.
`total_pairs`	Yes	Number of sentence pairs in the whole book.
`source_language`	Yes
`target_language`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the lower bar applies, and the description still adds real behavior: ordered sentence pairs, romanization inclusion, `has_more` continuation, and `total_pairs` as book length. It doesn't cover edge cases like an unknown or non-public book_id, but the core behavior is well disclosed.

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?

Three sentences, front-loaded with the resource and its payload, then pagination mechanics, then a single clarifying field. Every clause carries information an agent would otherwise have to guess.

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?

With an output schema present, the description doesn't need to enumerate return fields, yet it still names the key ones (sentence pairs, romanization, has_more, total_pairs), making the tool fully callable as specified. The only gap is failure behavior for a missing or private book_id.

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 would be 3; the description earns above that by explaining the relationship between `offset` and `limit` across successive calls and by scoping `book_id` to public books. It adds coordination semantics the per-field schema text does not express.

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 gives a specific verb and resource — reading a public audiobook's bilingual text — and immediately specifies the shape (sentence pairs with translation and romanization, in reading order). It's clear what the tool returns, but it never distinguishes itself from the close sibling get_book, which an agent could easily confuse with fetching a book's contents.

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?

Pagination guidance is explicit and actionable: return at most `limit` pairs from `offset`, then continue with offset + limit while `has_more` is true. What's missing is routing guidance — no statement of when to call this versus get_book or search_books, which matters given the name overlap.

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

All Bibooks 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.