Fetch Vox top stories with titles, URLs, summaries, authors, and publication times; pass item URLs to vox-article for full article bodies.
Get Vox top stories. Returns the latest Vox top stories with no parameters. Each item has its title, URL, summary, author and publication time. Item URLs can be passed to vox-article for the body.
| 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 full burden. It discloses that the operation takes no parameters and returns a list of items with specific fields, which is helpful. It does not cover behavioral traits like ordering guarantees, freshness/refresh behavior, or result limits, which matters for a 'latest stories' feed.
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?
Three short sentences, front-loaded with the core purpose, followed by return structure and a cross-tool pointer. Every sentence adds value with no filler.
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 parameterless read tool with no output schema, the description adequately covers purpose, the shape of returned items, and the follow-up tool. The only gap is not distinguishing itself from similar Vox headline/list siblings.
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, so baseline is 4. The description reinforces this by stating 'with no parameters', leaving no ambiguity for the agent.
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 Vox top stories') and even clarifies that it takes no parameters. It is clear what the tool does, but it does not differentiate itself from close siblings like vox_headlines or vox_sections, so an agent cannot tell from the description alone why to pick this over those.
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?
There is a useful workflow hint that item URLs can be passed to `vox-article` for the body, which is genuine cross-tool guidance. However, there is no explicit when-to-use/when-not guidance relative to siblings like vox_headlines, so usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.