scholar-mcp

Search Books

search_books

Read-only

Find books by title, author, or free text to retrieve scholarly references and prior art from Open Library.

Instructions

Search for books by title, author, or free text.

Uses Open Library. Prefer title and author over query — they use dedicated indexes and return far better results.

Open Library is politeness-rate-limited, so a busy moment may answer with a job handle to poll using get_job_result instead of the results themselves.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results to return (max 50).
`query`	No	Free-text fallback. Use ``title``/``author`` when known.
`title`	No	Book title or partial title (recommended).
`author`	No	Author name (recommended).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.10.0Sep 8, 2026
- addedOutput schema / additionalProperties
```
Added value: +true
```
- removedOutput schema / properties
```
Removed value: -{
-  "result": {
-    "type": "string"
-  }
-}
```
- removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```
- removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```
First observedv1.9.0Aug 10, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses the rate-limit behavior and the possibility of returning a job handle instead of direct results. This is valuable behavioral context not present in annotations.

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, each carrying distinct information: the search modes, the preferred parameters, and the rate-limit fallback. No redundant or filler content.

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 a fully described input schema and an output schema present, the description covers the core usage, the recommended parameter choices, and the edge case of rate limiting. Everything an agent needs to decide when and how to call this tool is addressed.

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?

The schema already fully describes each parameter with recommended usage. The description adds the cross-parameter guidance to prefer title/author over query, which slightly exceeds the schema's individual descriptions. No contradictions or missing clarifications.

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?

Clearly states the action (search) and resource (books), and lists the three supported search modes: title, author, or free text. Leaves no ambiguity about the tool's purpose.

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

Usage Guidelines5/5

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

Explicitly advises preferring title and author over query for better results, and warns about rate limiting with a fallback to polling via get_job_result. This gives concrete, actionable guidance for when and how to use the tool.

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