Fetch top business and finance stories from This Is Money’s public RSS feed. Returns current headlines as clean JSON for monitoring and analysis.
Get This Is Money top stories. Returns fresh This Is Money 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 provided, so the description carries the full burden. It discloses that the tool returns stories from an RSS feed, implying a read operation, but lacks detail on potential limitations (e.g., number of stories, freshness guarantees, pagination) or side effects. Minimal behavioral context is given.
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 fluff. The primary action and resource are front-loaded, and the RSS source is stated efficiently. Every sentence 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 zero-parameter tool with no output schema and no annotations, the description provides a clear and sufficient statement of what the tool does. The only missing piece is the return format or structure, but for a simple feed fetch this is likely adequate.
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 input schema is empty. The baseline for 0 params is 4, and the description adds no parameter-specific meaning because there are none to document. The description's mention of 'top stories' provides context but is not parameter-related.
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 verb 'Get' and resource 'This Is Money top stories', and specifies it returns fresh stories from the public RSS feed. It conveys the core function but does not explicitly differentiate from sibling tools like thisismoney_article or thisismoney_headlines, leaving some ambiguity about scope.
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 provides no guidance on when to use this tool versus alternatives. There is no mention of exclusions (e.g., 'for a specific article, use thisismoney_article') or context for when top stories are preferred. An agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.