Get Fortune top stories from public RSS feed. Returns clean JSON for fresh business news headlines, enabling quick access to current Fortune articles.
Get Fortune top stories. Returns fresh Fortune stories from the 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 of behavioral disclosure. It discloses that it returns fresh stories from an RSS feed, indicating a read-only operation and data source, but does not describe the output structure, pagination, or any rate limiting. This is adequate but not rich.
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 concise sentences, front-loaded with the primary action ('Get Fortune top stories') followed by a brief source clarification. Every word earns its place, with no fluff.
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 the simplicity of the tool (no parameters, no output schema), the description covers the essential function and data source. It could mention the expected return format, but for a straightforward fetch of top stories, it is sufficiently complete for an agent to call it.
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 has zero parameters, and the schema is empty. The baseline for 0 parameters is 4. The description adds no parameter-specific details, but none are needed, so the baseline holds.
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 clearly states the tool retrieves Fortune top stories, specifying a distinct resource and a verb ('get'). It also mentions the source (public RSS feed). However, it does not explicitly differentiate from sibling tools like fortune_headlines or fortune_news, which could be ambiguous, though 'top stories' hints at a curated selection.
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 such as fortune_headlines, fortune_article, or fortune_sections. There are no exclusions or conditions mentioned, so an agent has no basis to choose between similar news-fetching tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.