Fetch fresh headlines from a selected Global News RSS section by passing the section slug, returning clean JSON for news monitoring or display.
Get Global News section headlines. Returns fresh headlines from one public Global News RSS section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Global News RSS section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It usefully discloses that the data comes from a public RSS feed and is 'fresh,' which implies no auth and current content. However, it does not describe output format, headline fields, limits, or error behavior, leaving some uncertainty about what the agent will receive.
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 two short sentences with no redundant phrasing. The core action and resource are front-loaded, and the additional detail about public RSS freshness 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 single-parameter tool with a fully specified enum and no output schema, the description provides enough context for an agent to call it correctly: it identifies the resource, scope, and freshness. It does not describe response structure, but the simplicity of the tool and the schema's completeness make this a minor 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% and the section parameter is already well-documented with an enum and a description ('Global News RSS section slug'). The description adds minimal semantic value beyond reinforcing that the tool returns section headlines, so the baseline score of 3 is appropriate.
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 action ('Get') and resource ('Global News section headlines'), and adds that it returns fresh headlines from a public RSS section. It does not explicitly differentiate from sibling tools like globalnews_news or globalnews_sections, so it stops short of full sibling distinction.
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 this tool is for fetching headlines by section, but it provides no guidance on when to use it instead of related tools such as globalnews_sections (for listing sections) or globalnews_news (for broader news content). No alternatives or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.