Get CBC News top stories from the public RSS feed, omitting live-update pages.
Get CBC News top stories. Returns fresh CBC News top stories from CBC's public Top Stories RSS feed. Live-updates pages are omitted.
| 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 data source (public Top Stories RSS feed), freshness, and the fact that live-updates pages are omitted. It does not describe pagination, count limits, or response structure, but for a zero-parameter read-only feed fetch the disclosed context is reasonably adequate.
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 compact and efficient: two sentences with no filler. The main action and resource are front-loaded in the first sentence, and the second sentence adds a useful behavioral caveat without redundancy.
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 simple zero-parameter tool with no output schema and no annotations, the description provides enough core information: what is returned, the source feed, and an important exclusion. It could be slightly richer about output format or limits, but nothing critical is missing for invoking it correctly.
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?
There are zero parameters in the input schema, so the baseline is 4. The description appropriately avoids inventing parameter detail where none exists.
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 verb and resource: 'Get CBC News top stories' from 'CBC's public Top Stories RSS feed.' This distinguishes it from article/author/section tools but not explicitly from the similarly named cbc_headlines sibling, so it slightly misses full sibling differentiation.
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 implies usage by stating what it returns, but it gives no guidance on when to choose this tool over alternatives such as cbc_headlines, cbc_news, or other news headline tools. There is no explicit when-to-use, when-not-to-use, or reference to a sibling alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.