Retrieve 20 recent Mediaite top stories across the site, including title, URL, summary, publication time, and author, with no parameters required.
Get Mediaite top stories. Returns the 20 most recent Mediaite stories across the site, with no parameters. Each item has its title, canonical URL, summary, publication time and author. Use mediaite-headlines to read a single category instead.
| 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 the fixed result count (20), that no parameters are needed, and the exact fields returned (title, canonical URL, summary, publication time, author). It does not mention read-only safety or pagination, but for a parameterless news feed this is substantial.
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?
Four tight sentences: purpose, result count and parameterless nature, field list, and alternative routing. All information is front-loaded and every sentence adds value.
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?
With no output schema or annotations, the description provides enough to call the tool correctly: what it returns, how many items, what fields, and when to use a sibling. No gaps for a zero-parameter tool.
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 0 parameters, so the baseline is 4; the description reinforces this with 'with no parameters'. There are no parameter details to add, and the schema is empty.
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 specific verb ('Get') and resource ('Mediaite top stories'), and distinguishes scope from the sibling `mediaite-headlines` by noting it returns across the site rather than a single category. An agent can tell it apart without opening the schema.
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?
Explicitly names the alternative (`mediaite-headlines`) and the condition that selects it ('to read a single category instead'), telling the agent when to prefer that tool. No exclusions for other siblings, but the key routing is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.