Skip to main content
Glama

NewsMCP

by com.newsmcp

get_story

Expand one story: full summary, classification, actors, and source links.

Use this after any search, when the user wants more than the digest line for a particular story. It is the only tool that can return a story's complete source list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoOptional NewsMCP API key for this call; forwarded upstream as x-api-key. Only one request may be in flight at a time, so never call in parallel.
event_idYesThe `event_id` of a story from an earlier result (e.g. `evt_...`). A story folded into a more complete one answers 404 naming its replacement id — fetch that instead.
include_sourcesNoFalse (default) returns a sample of source links; True returns every one. A large story can carry several hundred, so leave this off unless the user asked for the full list. This is the only place the complete list is available — the search endpoints cap it.
response_formatNomarkdown (default), text, or json. Pass the format the user asked for rather than reformatting afterwards.markdown

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the transparency burden. It discloses that the tool expands a story into a full record and uniquely returns the complete source list. It is clearly a read operation with no side effects implied. It does not mention the 404-with-replacement-id behavior, but that is documented in the event_id parameter description, so the agent is not misled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences plus a usage note, with the core purpose front-loaded. Every sentence earns its place: it states what the tool returns, when to use it, and what makes it unique. There is no fluff or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-required-parameter expansion tool with no output schema, the description is complete: it lists the return contents, gives the trigger condition, and flags the unique full-source-list capability. The schema covers parameter details like response_format and the api_key concurrency constraint, so nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters thoroughly. The description adds no additional parameter-level meaning beyond what the schema provides, which matches the baseline of 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Expand one story.' It then lists the concrete contents returned (full summary, classification, actors, source links) and contrasts itself with the 'digest line' from search results, making its purpose unambiguous and distinguishing it from sibling tools like news.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: 'Use this after any search, when the user wants more than the digest line for a particular story.' It also states the tool's unique capability as the only source of the complete source list. It does not name alternative tools explicitly, but the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NewsMCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Each tool has a clear primary role: news searches digests, get_story expands one story, check_coverage verifies claim independence, check_limits reports quotas, and check_health tests API connectivity. The only mild overlap is that news can fetch by id while get_story also expands a story, but their descriptions make the distinction clear.

Naming Consistency3/5

Three tools use a consistent check_ prefix, and get_story follows a verb_noun pattern, but the primary search tool is simply named news, which breaks the convention. The naming is readable and all lowercase snake_case, but the mix of check_, get_, and a bare noun is not fully consistent.

Tool Count5/5

Five tools is well-scoped for a news-focused MCP server: search, detail expansion, coverage verification, usage limits, and health checking each earn their place. There is no bloat or obvious redundancy.

Completeness5/5

The tool surface covers the full intended workflow: search synthesized news, expand a story to full details, verify claim coverage, check live plan limits, and diagnose connectivity. Users can discover stories, dive deeper, and understand constraints without hitting dead ends.

Resources