Fetch Irish Times top stories from its public news feed and return headlines as structured JSON for news monitoring or content aggregation.
Get Irish Times top stories. Returns fresh Irish Times top stories from its public Irish news 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?
With no annotations, the description carries the transparency burden. It discloses that stories are 'fresh', come from a 'public' feed, and are returned as top stories, which implies a safe read operation. However, it does not describe output shape, count, or any limits or pagination behavior.
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 short and front-loaded: the first sentence states the action and the second adds freshness and source context. There is slight redundancy in repeating 'top stories', but the text is otherwise clutter-free.
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 tool without an output schema, the description covers basic purpose and source, but it omits any indication of the return format and does not clarify how this tool differs from irishtimes_headlines. It is minimally sufficient but leaves an agent guessing about output structure.
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 input schema has zero parameters, so there are no parameter meanings for the description to add; the no-parameter baseline applies.
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') with a clear resource ('Irish Times top stories') and adds source detail ('public Irish news feed'). It is not tautological, but it does not explicitly distinguish itself from sibling tools like irishtimes_headlines.
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: if you want fresh Irish Times top stories, this is the tool. However, it names no alternatives and gives no when-or-when-not guidance, leaving an agent to infer the distinction from nearby siblings like irishtimes_headlines or rte_news.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.