Retrieve the New York Post RSS section inventory to find available feeds for headlines. Use it to identify section names before requesting headline data.
Get New York Post RSS sections. Returns the public New York Post RSS section inventory used by the headlines endpoint.
| 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 provided, the description carries the full behavioral disclosure burden. It indicates the data is a public inventory, names the RSS source, and clarifies that the endpoint simply returns this inventory rather than mutating or filtering anything. It does not describe output structure, but for a simple no-parameter read operation this is adequate context.
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 sentences with no filler: the first names the operation and the second states what is returned and how it relates to the headlines endpoint. Every sentence contributes useful information.
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 zero-parameter tool with no output schema, the description is reasonably complete: it states the source, the public nature, and the downstream consumer. It could say more about the shape of the returned section inventory, but the low complexity makes the current description sufficient for correct invocation.
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 description needs to add no per-parameter meaning. The baseline of 4 applies; the description correctly implies this is a fixed inventory that requires no input.
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 uses a specific verb and resource — 'Get New York Post RSS sections' — and further clarifies the exact purpose by stating it returns the public section inventory used by the headlines endpoint. This clearly distinguishes it from sibling tools like nypost_article, nypost_author, nypost_headlines, and nypost_news.
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?
The description gives clear context: this tool supplies the RSS section inventory consumed by the headlines endpoint, which signals when an agent would need it. It does not explicitly state when not to use it or name alternatives, but for a zero-parameter inventory listing that is a minor omission.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.