Retrieve top stories from Mediaite's public news feed and return them as structured JSON for easy integration.
Get Mediaite top stories. Returns fresh Mediaite top stories from the public news 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 does mention 'public news feed' (implying no auth) and 'fresh' (recency), but it does not describe the return format, pagination, or any limitations. For a read operation, more transparency about output structure is expected.
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 redundant wording. The first sentence states the action, the second adds 'fresh' and 'public news feed'. It is front-loaded and efficient, earning a high score for conciseness.
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?
There is no output schema, so the description should describe the return value. It only says 'top stories' without specifying the structure (e.g., list of titles, objects with metadata). This is a significant gap for an agent that needs to consume the result. It is minimally adequate for a no-param feed but lacks essential detail.
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, so the schema coverage is effectively 100%. With no parameters to document, the description does not need to explain any. The baseline of 4 is appropriate given no parameters exist.
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 action ('Get Mediaite top stories') and the resource (Mediaite). It is not a tautology and distinguishes the basic intent, but it does not differentiate from siblings like mediaite_headlines or mediaite_news, which could overlap in functionality.
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. Sibling tools like mediaite_headlines, mediaite_sections, and mediaite_article exist, but the description gives no context for selecting this one over them, nor any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.