Fetch the 30 newest Raw Story articles across all sections, returning titles, URLs, summaries, publication times, authors, and lead images for quick news monitoring.
Get Raw Story top stories. Returns the 30 newest Raw Story stories across all sections. Takes no parameters. Each item has its title, story URL, a lead-paragraph summary capped at 500 characters, publication time, author byline and lead image.
| 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 behavioral burden. It discloses helpful traits such as no parameters and a fixed return of 30 newest stories with capped summaries, but it does not discuss authentication needs, rate limits, caching, or whether the feed is read-only in explicit terms.
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 three efficient sentences with the core purpose front-loaded. Every sentence adds useful information: what it returns, that it needs no parameters, and what each item contains.
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 no-parameter news feed with no output schema, the description is complete enough to call correctly. It explains the result count, section scope, and item-level fields including the 500-character summary cap.
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 has zero parameters, which sets the baseline score at 4. The description reinforces this by stating 'Takes no parameters', matching the empty input schema, though no additional 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?
The description states a specific verb and resource ('Get Raw Story top stories') and clarifies scope ('30 newest Raw Story stories across all sections'). It does not explicitly differentiate from siblings such as rawstory_headlines or rawstory_sections, but the resource is clear enough for an agent to understand what is returned.
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 no guidance on when to use this tool versus alternatives. The description says it takes no parameters and returns 30 newest stories, but never names a sibling tool or gives a condition for choosing this over rawstory_headlines, rawstory_article, or rawstory_sections.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.