Fetch top Business Insider stories from the public feed to monitor headlines and news trends in structured JSON.
Get Business Insider top stories. Returns fresh Business Insider 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?
No annotations are present, so the description carries the burden of behavioral disclosure. It usefully notes the source is a 'public RSS feed,' implying a public, read-only operation. However, it does not disclose output format, story count, recency bounds, or any rate limits, leaving some uncertainty.
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 filler. It front-loads the core purpose and adds the source detail efficiently.
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, the description covers what it returns and where the data comes from. The lack of an output schema means some return-structure details are unspecified, but for a simple top-stories feed this is a minor gap.
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, so parameter documentation is not needed. The description's mention of the RSS feed and top stories provides sufficient context for a no-input tool.
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 specific verb and resource: 'Get Business Insider top stories.' It also identifies the data source as the public RSS feed, which clarifies what kind of data is returned. However, it does not explicitly distinguish this from the sibling businessinsider_headlines, leaving some potential overlap.
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?
There is no guidance on when to use this tool versus alternatives like businessinsider_headlines, businessinsider_article, or businessinsider_sections. The description implies it is for top stories, but does not state exclusions or name any sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.