weread-mcp

章节目录

get_book_chapters

Read-only

Retrieve a book's chapter list with hierarchy, word counts, and paid status. Use returned chapter IDs to fetch highlights or underlines per chapter.

Instructions

获取书籍章节目录（/book/chapterinfo）。

    `chapters[].level` 是目录层级（1=一级标题），展示时按层级缩进并标注字数与付费状态
    （`price=0` 免费、`paid=1` 已购买）。

    `chapters[].chapterUid` 是 `get_chapter_underlines` / `get_best_highlights` /
    `get_highlight_reviews` 的入参，需要按章节查划线时先用本工具取得。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`book_id`	Yes	书籍 ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context about the output: chapters[].level indicates hierarchy, price=0 is free, paid=1 is purchased, and chapterUid is a required input for three named sibling tools. This goes beyond annotations and enriches the agent's understanding of the return structure and downstream usage.

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?

The description is compact and every sentence carries useful information, but the formatting with line breaks and backticks makes it slightly dense. It is still front-loaded with the core purpose, followed by field semantics and cross-tool usage, so it largely earns its place.

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

Completeness5/5

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

Given a single parameter, read-only annotations, an output schema, and a clear cross-tool dependency chain, the description is complete. It explains the meaning of key fields, how to interpret payment status, and why chapterUid matters, leaving no obvious gap for an agent to invoke the tool correctly.

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?

The input schema has 100% coverage and describes book_id as '书籍 ID', so the description need not repeat it. The description does not add any extra meaning about the parameter itself, earning the baseline score of 3 for high schema coverage.

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 opens with '获取书籍章节目录' (get book chapter table of contents), clearly identifying a specific verb and resource. It further specifies the intended use as a prerequisite for calling get_chapter_underlines, get_best_highlights, and get_highlight_reviews, distinguishing it from the listed sibling tools and giving an agent clear grounds for selection.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool: '需要按章节查划线时先用本工具取得' (when looking up underlines by chapter, first obtain chapterUid with this tool). This names dependent sibling tools and gives a concrete conditional, providing strong usage guidance beyond mere purpose.

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