list_news按日期和关键词查询公开新闻，默认北京时间今天，按发布时间从新到旧排序。有图的条目带 cover（站内图片地址与图源）。text 为已排版 Markdown（含封面图语法）；前若干条有 cover 时尽量附缩略图 image 块（有 image 时省略 structuredContent）。availableDates 为可查日期，nextOffset 非空表示还有下一页。
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | ||
| limit | No | ||
| query | No | ||
| offset | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description provides highly valuable technical and behavioral traits beyond the annotations. It details specific content formats (Markdown, cover URLs, structured image blocks) and logic (when an image block replaces structured content), giving the AI deep context on the expected result.
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 single paragraph is dense but logically structured: first stating the core function, then describing content structure, and finally explaining operational logic (pagination). Every sentence adds specific functional detail.
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?
Given that there is no output schema provided, the description is exceptionally complete. It explains the structure of the data, including the specific format of text (Markdown) and the mechanism for retrieving subsequent pages ('nextOffset').
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?
Since the schema description coverage is 0%, the description does a good job of contextualizing the parameters. It explains that the 'date' is part of a set of 'availableDates' and how the output handles the offset via 'nextOffset', adding semantic meaning beyond the basic schema definitions.
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 tool clearly states its purpose: querying public news by date and keyword. It distinguishes itself from sibling tools like get_report by defining its scope as 'public news' rather than reports.
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?
It defines crucial default behavior (today's date, newest first sort). It also explains the pagination mechanism using 'nextOffset' to guide when the agent should continue querying. It lacks explicit 'when to avoid' guidance, but its description is very clear on how it functions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.