Skip to main content
Glama
Xiaochengzi2048

find-a-book-mcp

search_books

Search Library Genesis for books by title, author, or keywords. Returns 5 results per page with details: title, author, year, language, format, size, and MD5 hash. Supports pagination and filtering by file extension.

Instructions

Search for books on Library Genesis (tries multiple mirrors automatically). Returns 5 results per display page with pagination support. Each book includes title, author, year, language, format, size, size_bytes, and MD5.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesBook title, author, or keywords
pageNoDisplay page number (1-indexed, 5 results per page)
extensionsNoFilter by format, e.g. ['epub', 'pdf']
Behavior4/5

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

Discloses automatic mirror switching, pagination behavior (5 results/page), and returned fields (title, author, etc.). With no annotations, this adequately informs agents of key behaviors, though rate limits or error handling are omitted.

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?

Two succinct sentences, each delivering key information: purpose/behavior in first, result format/pagination in second. No filler or repetition.

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?

Covers core functionality, mirror handling, pagination, and result fields. Lacks details on error states or empty results, but sufficient for typical search tasks given the parameter count and absence of output 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 100%, so baseline is 3. Description adds no new semantics for parameters beyond what schema provides; 'query' and 'page' are restated, 'extensions' is not mentioned. No value added over schema.

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?

Description clearly states the tool searches for books on Library Genesis, with specific verb 'search' and resource 'books'. It mentions automatic mirror retries, which adds clarity. Sibling tools (download_book, get_formats) indicate distinct purposes, so no confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives (download_book, get_formats). While the name implies search, the description does not contrast with siblings or state prerequisites, leaving the agent without context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Xiaochengzi2048/find-a-book-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server