Fetch current Mediaite headlines from any category, returning structured JSON data for your applications.
Get Mediaite section headlines. Returns fresh Mediaite headlines from one public category feed.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Mediaite category slug |
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 results are 'fresh' and from a 'public category feed,' which implies no auth, but it doesn't describe output structure, pagination, limits, or error behavior. This is minimal disclosure for a tool with no annotation safety net.
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?
Two short sentences with no filler; the key action and resource are front-loaded. Every word 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?
The tool is simple (one enum param, no output schema), but the description still leaves the return payload unspecified—agents don't know if they get titles, URLs, timestamps, or how many items. For a tool with no output schema, this is a meaningful 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?
Schema coverage is 100%, with the section parameter fully documented as a 'Mediaite category slug' and an enum of valid values. The description adds only that the feed is a 'public category feed,' which weakly ties the parameter to the feed selection. Baseline 3 applies since the schema carries the parameter semantics.
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 uses a specific verb ('Get') and resource ('Mediaite section headlines') and adds context that it pulls from a single public category feed. It is clear what the tool returns, though it doesn't explicitly distinguish itself from sibling tools like mediaite_news or mediaite_sections.
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 prefer this tool over alternatives. It doesn't mention sibling tools, exclusions, or use cases beyond the tautological 'get headlines.' An agent must infer that this is for section-specific Mediaite headlines.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.