Fetch Sky News top stories as structured JSON, including title, URL, summary, publication time, and image; pass an item URL to skynews-article for its body paragraphs.
Get Sky News top stories. Returns Sky News's latest top stories across the site. Takes no parameters. Each item has its title, URL, summary, publication time and image. Pass an item's URL to skynews-article for its body paragraphs.
| 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 behavioral burden. It usefully discloses the return shape (title, URL, summary, publication time, image) and that no inputs are required, but says nothing about result limits, ordering, auth, or pagination for a feed-style endpoint.
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?
Four short sentences, front-loaded with the purpose, followed by output shape and the handoff tool. Nothing is redundant and every sentence carries information.
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?
With no output schema and no annotations, the description compensates by enumerating the returned fields and stating the no-parameter contract. The main residual gap is whether the feed is paginated or capped, which an agent might need to know.
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?
Zero parameters, which is the baseline-4 case, and the description explicitly confirms "Takes no parameters," matching the empty schema. No further parameter meaning is needed.
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?
Names a specific verb and resource ("Get Sky News top stories") and clarifies scope with "across the site." It distinguishes itself from skynews_article by pointing there for body paragraphs, but does not differentiate from the sibling skynews_headlines, which an agent could easily confuse with "top stories."
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?
Gives clear context (latest top stories, no parameters) and an explicit follow-up path: pass an item's URL to skynews-article for body paragraphs. It stops short of stating when to prefer this over skynews_headlines or skynews_sections, so no true exclusions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.