Retrieve Daily Kos top stories and current staff-authored articles from the public RSS feed. Use it to track Daily Kos headlines as structured JSON.
Get Daily Kos top stories. Returns current staff-authored Daily Kos stories from its public RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It usefully discloses the data source (a public RSS feed) and that results are current, staff-authored stories, which implies a read-only, no-auth fetch, but says nothing about result limits, ordering, or how many stories are returned.
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 purpose is front-loaded and the source detail follows as supporting context. Every clause 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 feed reader with no output schema and no annotations, the description covers what is returned, whose content it is, and where it comes from. It stops short of explaining ordering or result volume, but nothing essential to invoking it is missing.
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 schema has no semantics to explain and the baseline is 4. There is nothing for the description to compensate for here.
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+resource (get top stories from Daily Kos) and identifies the source (public RSS feed) plus the content type (current staff-authored stories). It is clear what the tool returns, but it never distinguishes itself from the sibling dailykos_headlines or dailykos_article, so an agent must guess which of the three 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?
There is no explicit when-to-use guidance and no mention of alternatives such as dailykos_headlines or dailykos_sections, which occupy very similar territory. The agent must infer that "top stories" means the news feed rather than the headlines listing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.