Retrieve linux.do topic details and post floors by numeric ID or topic URL, with configurable post count and starting floor for pagination.
读取指定话题的详情与楼层正文。topic_id 可传数字 id，也可直接传 linux.do 话题 URL（如 https://linux.do/t/xxx/2885565/1，会自动取出 id）。posts=返回楼层数， start=起始楼层(1-based，用于翻页，如 start=21 取第 21 楼起)。返回含 total_posts(总楼数)。
| Name | Required | Description | Default |
|---|---|---|---|
| posts | No | ||
| start | No | ||
| topic_id | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
无注释，描述承担全部负担。它披露了topic_id的URL自动提取、分页参数及返回含total_posts，但未说明错误行为、权限要求或只读确认。对于只读操作，信息基本足够但不够深入。
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?
描述紧凑无冗余，先说明核心用途再详述参数，所有句子都承载信息。没有浪费字符。
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?
无输出模式，描述提到返回含total_posts但未描述完整结构。对于3个参数的简单只读工具，基本信息具备，但未覆盖错误处理或与其他工具的区分，完整性中等。
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?
模式覆盖率为0%，描述完全补偿。它解释了topic_id可接受数字或URL并自动提取ID，以及posts和start的用途、默认值和分页语义，远优于模式本身的类型定义。
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?
描述明确说明工具读取指定话题的详情与楼层正文，动词'读取'加资源'话题'，并解释了topic_id可传数字或URL。它清楚区分了基本功能，但未直接提及与兄弟工具如format_topic的差异，因此未达到最高分。
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?
描述提供了参数用法（posts、start）但未说明何时使用此工具而非search、format_topic等。没有上下文或排除条件，代理只能推测其适用场景。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.