mcp-ebook-read

Overview Schema Source Related Servers Discussions Admin

epub_list_images

List extracted images from an EPUB book, optionally scoped to an outline node. Use before reading images in multimodal workflows.

Instructions

List extracted images from an EPUB book, optionally scoped to an outline node. Use before epub_read_image in multimodal reading workflows.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "doc_id": "<doc_id>"
    },
    "name": "epub_list_images"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`doc_id`	Yes
`node_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.7Jul 13, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic function (listing images) and optional scoping, without mentioning read-only nature, return format, or any side effects. This is insufficient for a tool with no 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 two sentences long, front-loaded with the core function, and contains no unnecessary words. It is efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description gives the essential purpose and workflow hint, it lacks details such as output format, what qualifies as an image, or any limitations. The presence of an output schema partly mitigates this, but the description could be more informative for a tool with 3 parameters.

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

Parameters2/5

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

The input schema has 0% description coverage for parameters. The description only hints at node_id for scoping but does not clarify doc_id or limit. With 3 params and 1 required, more explicit parameter guidance is needed.

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 lists extracted images from an EPUB, with optional scoping by outline node. It distinguishes from siblings like epub_read_image and pdf_list_images by specifying the file type and workflow context.

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 explicitly advises using this tool before epub_read_image in multimodal workflows, giving a clear usage context. However, it does not mention when not to use it or alternative tools for similar tasks.

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