Fetch top stories from Global News (globalnews.ca) via its public RSS feed to get current headlines and article links.
Get Global News top stories. Returns fresh Global News (globalnews.ca) top stories from its public RSS 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 present, so the description carries the full burden. It only states that it returns fresh top stories from the RSS feed, without detailing output format, item count, pagination, or any rate limits. The behavioral disclosure is minimal and leaves important aspects (e.g., what 'top stories' looks like) unclear.
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 concise sentences with the primary action front-loaded. The description is efficient and contains no redundant or extraneous information, making it easy for an agent to parse and act on.
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 (no parameters, no output schema), yet the description does not explain the return structure or any limitations. It is adequate for understanding the basic action but leaves the agent guessing about the response format and how to consume the results, which is a notable gap given the absence of an output schema.
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?
With zero parameters, the schema is trivially covered (100%). The description adds no parameter-specific information, but the baseline for 0-parameter tools is 4, and the description does mention the data source (RSS), which is the only relevant context.
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 tool's purpose: get Global News top stories, with a specific resource (Global News RSS feed). It is unambiguous, but does not distinguish itself from sibling tools like globalnews_headlines or globalnews_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?
No guidance is provided on when to use this tool versus alternatives. The description does not mention any context, exclusions, or conditions that would help an agent choose between this and other news tools like globalnews_headlines or ctvnews_news.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.