scholar-mcp

Get Book

get_book

Read-only

Fetch book metadata by ISBN or Open Library ID, with cover size selection and optional cover download. Returns a job handle when rate-limited.

Instructions

Fetch book metadata by ISBN or Open Library ID.

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 record itself.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cover_size`	No	Cover size variant: ``"S"`` (small), ``"M"`` (medium), ``"L"`` (large). Defaults to ``"M"``.	M
`identifier`	Yes	ISBN-10, ISBN-13, Open Library work ID (e.g. OL1168083W), or edition ID (e.g. OL1429049M).
`download_cover`	No	If True, download and cache the cover image locally. Returns ``cover_path`` in the response. In read-only mode, returns ``cover_error`` instead.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.10.0Sep 8, 2026

removedInput schema / properties / include_editions

Removed value: -{
-  "default": false,
-  "description": "If true, fetch the work and list editions.",
-  "type": "boolean"
-}

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.4/5.0

Behavior4/5

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

ReadOnlyHint annotation is consistent; description transparently explains rate-limit behavior and download_cover side effects (cache, cover_error in read-only mode).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise and front-loaded with the core purpose, followed by a brief, relevant note on rate-limiting and job polling.

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 key aspects an agent needs: input formats, side effects of download_cover, read-only mode behavior, and rate-limit resolution; output schema exists so not all return details need explanation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters are described with formats/examples; schema coverage is 100% and description adds meaningful detail like cover_path/cover_error behavior.

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 fetches book metadata by ISBN or Open Library ID, distinguishing it from siblings like get_book_excerpt and search_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?

Mentions the polling fallback via get_job_result when rate-limited, giving practical usage context though not explicitly contrasting with alternatives.

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