Retrieve New York Post top stories via its public RSS feed, returning fresh headlines as structured JSON.
Get New York Post top stories. Returns fresh New York Post top stories from its public RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It discloses the data source ('public RSS feed') and freshness ('fresh'), adding some behavioral context. However, it doesn't mention any limitations, rate limits, or the structure of the returned data, which would be helpful.
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 two short sentences with no extraneous words. The key action and source are front-loaded, making it easy for an agent to quickly grasp the tool's purpose.
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 no-parameter tool, the description is sufficient: it states what is returned and the source. It doesn't detail the return format (e.g., list of article objects), but given the simplicity and the tool name, this is a minor gap. No output schema exists, so a bit more detail could be added, but it's not critical.
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?
There are zero parameters, so the schema provides no semantics. The description adds context about what is returned (top stories from RSS), but no parameter details are needed. Baseline for 0 params is 4.
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 states a clear verb ('Get'), a specific resource ('New York Post top stories'), and a source ('public RSS feed'). This is specific enough to distinguish from generic news tools, though it doesn't name sibling alternatives to disambiguate.
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 provided on when to use this tool versus alternatives like nypost_article or nypost_headlines. The description only states what it does, not the context or exclusions for use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.