scholar-mcp

Get Book

get_book

Read-only

Fetch book metadata by ISBN-10, ISBN-13, Open Library work ID, or edition ID, including cover images; if rate-limited, returns a job handle to poll for the record.

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

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 (such as ``OL1168083W``), or edition ID (such as ``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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.1.1Nov 5, 2026

changedInput schema / properties / identifier / description

Previous value: -"ISBN-10, ISBN-13, Open Library work ID (e.g.\nOL1168083W), or edition ID (e.g. OL1429049M)."New value: +"ISBN-10, ISBN-13, Open Library work ID (such as\n``OL1168083W``), or edition ID (such as ``OL1429049M``)."

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

Behavior4/5

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

Annotations already cover read-only/open-world/destructive flags, but the description adds the non-obvious operational trait that a rate-limited call may return a job handle rather than the record. That is genuinely new behavioral context; what's missing is any hint about how to tell the two response shapes apart.

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 sentences, front-loaded with the core purpose and followed by the single operational caveat worth knowing. 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?

Return values are covered by the output schema, and the one surprising behavior (job-handle fallback) is disclosed. Slightly more detail on how to recognize a job-handle response versus a record would make it complete.

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 description coverage is 100% and the schema already documents identifier forms, cover_size variants, and download_cover/cache behavior. The description adds nothing beyond it on parameters, so the baseline of 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?

Names a specific verb and resource ("Fetch book metadata") and the accepted identifier schemes, which distinguishes it from search_books and get_book_excerpt. It stops short of explicitly naming the sibling used when no identifier is known.

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?

The implicit precondition is clear (you must already hold an ISBN or Open Library ID), and the description explicitly names get_job_result as the alternative path when the call is throttled. No explicit exclusion such as "use search_books when you only have a title".

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