Bibooks

Get an audiobook

get_book

Read-onlyIdempotent

Get one public audiobook by id: title, author, languages, CEFR level, audience, length, and links to its reader page, audio and share image.

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

Name	Required	Description	Default
`book_id`	Yes	The book's id (the `id` field of a Book).

Output Schema

Name	Required	Description
`id`	Yes	Stable book id (a UUID).
`urls`	Yes
`level`	Yes	CEFR difficulty level. Null when the book has no level.
`score`	Yes	Community score: upvotes minus downvotes, never below zero.
`title`	Yes	Title as the publisher entered it.
`author`	Yes	Author as attributed by the book's publisher. Not verified by bibooks.org; treat it as a claim, not a fact.
`origin`	Yes	Where the text came from. Null when it is not one of the public origins.
`audience`	Yes	Intended audience. Null when not set.
`published_at`	Yes	When the book finished generating (ISO 8601, UTC). Null when unknown.
`speed_percent`	Yes	Speaking speed of the target-language audio, as a percentage of normal (100).
`source_language`	Yes	Content-language code of the original text (see GET /languages). Null when it was not recorded.
`target_language`	Yes	Content-language code the text was translated into.
`duration_seconds`	Yes	Length of the audio in seconds. Null when unknown.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 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, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds one genuinely useful trait, that only 'public' audiobooks are retrievable, but says nothing about behavior for non-public or invalid ids, which is the main open question for a fetch-by-id 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?

One front-loaded sentence that identifies the resource, the key, and the payload. Every clause earns its place and nothing is padded.

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 needn't explain return values, and rich annotations cover safety and idempotency. The only remaining gap is the 'public'-only constraint's consequence (not-found vs error for non-public books), which keeps it short of full completeness.

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 a single parameter with 100% schema description coverage ('the `id` field of a Book'), so the schema carries the semantics. The description only repeats 'by id' and adds no format, source-of-id, or lookup hint beyond that; baseline 3 applies.

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 specific verb and resource (get one audiobook by id) and enumerates the returned fields, which makes the retrieval scope concrete. It implicitly separates itself from the plural search_books/list tools by emphasizing 'one public audiobook', but 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?

Usage is only implied: an agent can infer this is the lookup-by-known-id path versus search_books. There is no explicit when-to-use/when-not statement, no mention of what to do if the id is unknown, and no routing to read_book or search_books as alternatives.

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.