uleszka

Czytaj dzieło z biblioteki

read_book

Read-only

Retrieves a public-domain book from the library in ~15,000-character parts. Use find_in_article or search first to locate the relevant section before reading.

Instructions

Returns the text of a public-domain book from the library, in parts of ~15000 characters. Books are long – use find_in_article(id, phrase) or search(scope='biblioteka') to locate the relevant part first.

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": {
      "id": "<id>"
    },
    "name": "read_book"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	id książki z list_library, np. „platon-kritias”
`part`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The readOnlyHint annotation already establishes this as a safe read. The description adds important behavioral context that annotations do not: the result is chunked into parts of about 15000 characters and users should locate the relevant part before reading. It does not cover boundary behavior for invalid part numbers, but the key operational trait is 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?

The description is two sentences, front-loaded with the return behavior and followed by actionable routing guidance. There is no filler, and the most important constraints are stated first.

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?

For a simple read tool with two parameters, no output schema, and readOnlyHint already covering safety, the description provides enough context: what is returned, how it is chunked, and how to find the right chunk. It could be slightly more complete by clarifying the part parameter's default or range, but that is already in the schema.

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 50%: id is documented with an example, but part has no schema description. The description compensates somewhat by explaining that the book is returned in ~15000-character parts and that the relevant part should be located first, which implies what part controls. It does not explicitly state numbering or boundary behavior, so the coverage gap is only partially filled.

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: it returns the text of a public-domain book from the library. It also specifies scope (public-domain books) and output granularity (~15000-character parts), which clearly distinguishes it from read_article and list_books.

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 guidance to locate the relevant part first using find_in_article(id, phrase) or search(scope='biblioteka'), and it explains that books are long. It lacks a direct when-not-to-use statement, but the alternative routing is clear enough for an agent to act on.

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

Deploy Server