mcp-ebook-read

by ArtiPyHeart

Overview Schema Source Related Servers Discussions Admin

Python

Local

read_outline_node

Read a specific chapter or node from an ebook outline to access detailed content or summaries for guided reading.

Instructions

Read one outline node or chapter directly. Prefer this for chapter summaries and guided reading after get_outline.

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>",
      "node_id": "<node_id>"
    },
    "name": "read_outline_node"
  }
}

Input Schema

Name	Required	Default
`doc_id`	Yes
`format`	No	markdown
`node_id`	Yes
`max_chunks`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.7Jul 13, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so full burden on description. Only states 'Read one outline node or chapter directly' with no additional behavioral details like side effects, permissions, or error conditions. Minimal transparency.

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?

Two concise sentences, front-loaded with purpose. No fluff, but missing essential parameter explanations.

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?

Adequate for a simple read tool with output schema existing, but lacks parameter descriptions and any behavioral context (e.g., max_chunks limit). Could be improved with parameter details.

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 description coverage is 0% and the description does not explain any parameters (doc_id, node_id, format, max_chunks). No value added for parameter understanding.

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?

Clearly states the tool reads one outline node or chapter directly and distinguishes from sibling get_outline by specifying use after get_outline. Verb 'read' and resource 'outline node' are specific.

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?

Provides clear guidance: 'Prefer this for chapter summaries and guided reading after get_outline.' This tells when to use and implicitly after getting the outline. Lacks explicit alternatives or exclusions but sufficient.

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