Fetch the newest site-wide comments, including associated comic, nested replies, and spoiler flags. Use the page parameter to browse older comment pages.
获取全站最新发布的一页评论，包括评论所属本子、递归回评和剧透标识。
参数: page: 评论页码，从 1 开始（默认值：1）。
返回: 包含当前页码、分页总数、评论数量和评论列表的字典。 HTML 客户端不提供 total 和 page_count，此时对应字段为 null。
| Name | Required | Description | Default |
|---|---|---|---|
| page | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the transparency burden. It discloses pagination semantics, the returned dictionary fields, and a behavioral nuance: HTML clients receive null for total and page_count. This is useful context beyond a simple read-only statement, though it does not discuss auth or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and well-structured with '参数' and '返回' sections. Every sentence adds information: what the tool does, what the parameter means, and what the return shape is. There is no filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity tool with one optional parameter and an output schema, the description covers the essential invocation details: pagination, return structure, and client-specific null behavior. It does not provide routing context or mention authentication prerequisites, but those are secondary for this simple read operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It does: the '参数' section defines page as a comment page number starting from 1 with a default value of 1, which goes beyond the schema's type/default. The single parameter is fully described, but no examples or edge cases are given.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('获取全站最新发布的一页评论') with a specific resource and scope: site-wide latest comments. It also lists the main payload contents (parent album, recursive replies, spoiler flags). It does not explicitly name or contrast with the sibling get_album_comments, though '全站' implies a site-wide scope rather than an album-scoped one.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives. A sibling tool get_album_comments exists, but the description does not mention it or provide any selection criteria. The agent must infer that this tool is for site-wide comments and the sibling is for album-specific comments.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.