Retrieve The Sun's current top stories in structured JSON with titles, URLs, summaries, authors, publication times, and images for quick news monitoring.
Get The Sun top stories. Returns the current top stories from The Sun. It takes no parameters. Each item has its title, URL and, where available, a summary, author, publication time, image URL and type. Use the headlines endpoint to read one section.
| 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 burden, and it does disclose the result shape (title, URL, optional summary, author, publication time, image URL, type) in place of a missing output schema. It does not state read-only semantics, freshness, auth, or rate limiting, which are low-risk omissions for a headline list but leave minor gaps.
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?
Front-loads the scoping and the sibling routing, and the field inventory earns its place given no output schema. The first two sentences, however, restate the same fact ('Get The Sun top stories' vs 'Returns the current top stories from The Sun'), which is wasted space.
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 read tool with no annotations and no output schema, the description covers purpose, routing, and the fields an agent will receive. Only minor behavioral details (update cadence, read-only framing) are absent.
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 per the rubric. The description also confirms 'It takes no parameters', so an agent will not hunt for missing inputs.
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?
States a specific verb and resource ('Get The Sun top stories') and pins the scope as current top stories. It also differentiates from the sibling headline tool by noting 'Use the headlines endpoint to read one section', so an agent can tell sun_news (whole-site top stories) apart from sun_headlines (single section) without opening a schema.
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?
Explicitly routes the agent to the alternative ('Use the headlines endpoint to read one section') with the condition that selects it. There is no statement of when this tool is the wrong choice beyond that single case, but the useful context is present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.