weread-mcp

阅读进度

get_reading_progress

Read-only

Retrieve a book's reading progress to see completion percentage, reading time, and finish date. Useful for tracking reading status in WeChat Reading.

Instructions

获取某本书的阅读进度（/book/getprogress）。

    关键口径：
    - `book.progress` 是 0-100 的**整数百分比**，1 表示 1%（不是 100%）；展示必须带 `%`。
      只有 `progress=100` 且存在 `book.finishTime` 才代表读完。
    - 累计阅读时长看 `book.readingTime`（秒），展示转「X小时Y分钟」。
      `book.recordReadingTime` 是朗读/记录类时长，普通阅读通常为 0，**不要**拿它当阅读时长。
    - `book.updateTime` / `book.finishTime` 是 Unix 时间戳，展示转 `YYYY-MM-DD`。

    返回中的 `_computed` 是本服务端按上述规则算好的展示值。

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.2/5.0

Behavior5/5

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

注释已声明readOnlyHint=true，描述进一步补充了数据解释规则：progress为0-100整数百分比、finishTime条件、readingTime与recordReadingTime的区别、时间戳转换，以及_computed字段的预计算含义，这些远超注释提供的信息，且未与注释矛盾。

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?

描述采用分点结构，信息密集但每个要点都有价值（进度、时长、时间戳、计算字段），没有冗余。稍长但针对复杂语义是合理的。

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?

尽管存在输出schema，描述仍解释了关键字段的语义和转换规则，确保agent能正确解读数据。覆盖了所有可能误用的点（如百分比、时间单位），完整无缺。

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?

book_id在schema中已有描述（书籍ID），覆盖率为100%，描述未额外解释参数格式或用法，但基于schema已足够，基线3分。

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?

描述明确说明“获取某本书的阅读进度”，动词+资源清晰，且与兄弟工具（如get_read_stats、get_reading_overview）在语义上区分明显，因为它专注于单本书的进度细节。

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

Usage Guidelines3/5

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

描述未提及何时使用该工具而非其他替代品，也未说明排除条件。虽然从名称和上下文中可推断用途，但没有显式指导，agent可能需要自行判断。

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