Skip to main content
Glama
caelum29

calibre-mcp

by caelum29

Get book figures

calibre_get_figures
Read-only

List an ebook's figures with captions and page numbers, then fetch up to three selected figures as images to view them directly.

Instructions

List a book's figures — images the text references, identified by caption (Figure 1-2 / Рис. 3.1) — with page + caption per figure, then fetch chosen ones as images via indexes (≤3 per call). Captions let you pick figures before spending image tokens. In MCP Apps hosts the fetched figures also render for the user in an in-chat viewer, so you can point at them by figure number — but describe only what the pixels you received actually show.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
bookIdNo
detailNoImage resolution: standard ≤1024px longest side (default), high ≤1568px.standard
formatNoSource format override (epub or pdf). Default: epub if present, else pdf.
indexesNoFigure indexes from a previous list call — returns those figures as images (≤3 per call). Omit to list. Indexes are per-format; re-list after changing format.
libraryNo
include_uncaptionedNoAlso list/fetch images with no caption (covers, decorations, equation images).
Behavior4/5

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

The description adds behavioral details beyond annotations (readOnlyHint, openWorldHint): the ≤3 images per call constraint, platform-specific rendering in MCP hosts, and the caveat to describe only what pixels show. It does not contradict 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?

The description is concise and well-structured: first sentence captures core functionality, then elaborates on caption usage, platform behavior, and a crucial caveat. No wasted words.

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?

Given no output schema, the description adequately explains list output (page + caption) and fetch output (images). It includes constraints and a usage caveat. Minor gaps like error handling or index validation are omitted but acceptable for this tool.

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?

With 57% schema description coverage, the tool description adds meaning for key parameters: explains indexes come from a previous list, limits to ≤3, and defines detail resolution sizes. It also clarifies format default behavior. However, parameters like id, bookId, and library remain partially explained.

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 clearly states the tool's dual purpose: listing figures with captions and page numbers, then fetching images by index. It distinguishes itself from siblings like calibre_get_book or calibre_get_content by focusing specifically on figures.

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 description provides clear context on when to list vs. fetch ('Omit to list' for indexes), and advises using captions to pick figures before spending image tokens. However, it does not explicitly state when not to use this tool or compare with alternatives.

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/caelum29/calibre-mcp'

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