mcp-ebook-read

Overview Schema Source Related Servers Discussions Admin

pdf_read_figure

Access a specific figure from a PDF by providing document and figure IDs, returning the figure path, caption, and nearby text for analysis.

Instructions

Read one extracted PDF figure with local path, caption, nearby context, and diagnostics.

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>",
      "figure_id": "<figure_id>"
    },
    "name": "pdf_read_figure"
  }
}

Input Schema

Name	Required	Description	Default
`doc_id`	Yes
`figure_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.7Jul 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description fully carries the behavioral burden. It states the tool is read-only ('Read') and lists outputs, which is helpful but lacks details on auth, permissions, or side effects. 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?

Single sentence, no filler words. Front-loaded with verb and resource. Every word earns its place.

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?

Description covers the output but omits parameter explanations, which are essential given the lack of schema descriptions. For a simple tool with an output schema, this is minimally adequate but leaves gaps.

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

Parameters1/5

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

Schema coverage is 0%, meaning the schema provides no descriptions for doc_id or figure_id. The description does not explain these parameters, leaving the agent without guidance on what values to supply. This is critical for successful invocation.

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 uses specific verb 'Read' and resource 'extracted PDF figure', and lists return fields (local path, caption, nearby context, diagnostics). This clearly distinguishes it from sibling tools like pdf_read_image or pdf_read_table, which handle different entity types.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., pdf_read_image for raw images, pdf_read_table for tables). No prerequisites or exclusions mentioned.

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