Fetch top stories and opinion articles from Blaze Media's public RSS feed, returning fresh news in structured JSON for quick updates.
Get Blaze Media top stories. Returns fresh news and opinion stories from the public Blaze Media RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses that data comes from a public RSS feed (implying no auth) and that it is a read of fresh stories, but it omits return volume, pagination, and freshness/update cadence, leaving behavioral gaps.
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?
Two tight sentences with zero waste, and the core purpose is front-loaded. Every clause earns its place.
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 simple zero-param feed tool with no output schema and no annotations, the description covers source, content type, and freshness adequately. Minor gaps around result count and item structure remain but are not critical 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?
The tool takes zero parameters, so there is nothing for the description to compensate for; baseline 4 applies. The empty schema is consistent with the description's claim of a simple feed fetch.
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?
States a specific verb and resource ('Get Blaze Media top stories') and clarifies content type (news and opinion stories). It does not, however, explicitly differentiate itself from the sibling theblaze_headlines, which an agent could easily confuse with 'top stories'.
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?
Usage is implied — a zero-parameter feed tool is obviously called to retrieve current Blaze Media content — but there is no explicit when-to-use guidance or distinction from theblaze_headlines/theblaze_sections. No exclusions or prerequisites are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.