Get the current top stories from News24. Access titles, canonical URLs, and images for both freely readable and subscriber-only news content.
Get News24 top stories. Returns the current News24 top stories, with no parameters. Each item has a title, canonical URL and image. type is subscriber when News24 marks the story subscriber-only and is omitted for freely readable stories.
| 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 and no output schema, the description carries the full burden, and it partially meets it by describing the return shape (title, canonical URL, image) and the meaning of the `type` field (subscriber-only marker). It does not cover pagination, result count, or any auth/rate-limit behavior.
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?
Three compact sentences, front-loaded with the purpose and then the return details. Every sentence adds distinct information with no padding.
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 parameterless feed tool with no output schema, the description is nearly self-sufficient: it names the resource and enumerates the returned fields including the conditionally-present `type`. Only missing details are volume/pagination of the returned list.
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 the baseline is 4; there are no parameter semantics to explain beyond the explicit note that it operates 'with no parameters.'
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 clear verb+resource: 'Get News24 top stories' returning current top stories. However, it does not distinguish this from the sibling news24_headlines, which is presumably a very similar concept, leaving the agent to guess which endpoint to pick.
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 when-to-use guidance and no mention of alternatives or exclusions. Given near-identical siblings (news24_headlines, news24_sections), the absence of any routing hint is a real gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.