Fetch current VICE top stories with title, URL, summary, author, publication time, and lead image. Pass an item URL to vice-article to read the full story.
Get VICE top stories. Returns the latest VICE stories with no parameters. Each item has its title and URL, plus summary, author, publication time and lead image when the outlet provides them. Pass an item URL to vice-article to read the story.
| 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 and that optional fields appear only 'when the outlet provides them', but it omits auth needs, rate limits, ordering, and 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?
Three compact sentences front-load the purpose, then add return details and a clear next action. Every sentence contributes information without repetition or padding.
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 simple parameterless news list with no output schema, the description covers purpose, return fields, and follow-up routing. It is nearly complete, though it could mention item count or pagination if those matter for agent planning.
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 tool takes zero parameters, so there are no parameter semantics to clarify. The description explicitly notes 'with no parameters', which matches the empty schema and meets the baseline for a parameterless tool.
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 clear verb ('Get') and resource ('VICE top stories'), and names the downstream sibling `vice-article` for reading individual stories. It does not explicitly distinguish itself from the closely related `vice_headlines`, so it falls short of a 5.
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?
Implies usage by stating it returns 'latest VICE stories with no parameters' and tells the agent to pass an item URL to `vice-article`. It does not say when to prefer this over `vice_headlines` or other VICE list tools, leaving routing to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.