Skip to main content
Glama
NewsCatcher MCP

NewsCatcher MCP

Official

Get a story

get_story
Read-onlyIdempotent

Retrieve all coverage for a news story, including article counts, publishers, dates, headlines, links, and earliest reports to gauge story size, find original sources, or collect event coverage.

Instructions

Every article of one story (the coverage of one event) from search_news: how many newsrooms covered it, when it first and last appeared, each article's publisher, date, headline and link (best sources first), and the earliest articles. Use it to gauge how big a story is, find the original or most authoritative source, or collect all coverage of an event. 1 credit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "story_id": "<story_id>"
    },
    "name": "get_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoArticles to list (default 20, up to 500).
formatNotext (default, compact) or json (machine-readable).text
story_idYesA story id from a search_news result (the "story" field).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered by structured data. The description adds genuinely non-redundant behavior: the operation costs '1 credit', results are ordered 'best sources first', and the earliest articles are surfaced. It does not discuss truncation beyond the limit or what happens with a stale story_id.

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

Conciseness4/5

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

It is front-loaded with the return payload, followed by usage contexts and a one-token cost note, with virtually no filler. The opening sentence is a dense comma-separated inventory, which is efficient but slightly harder to scan than a short lead sentence plus bullets.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing return values, and it does so field by field, which is exactly what an agent needs before calling. The remaining gap is pagination/truncation semantics for limit values up to 500, which are not explained anywhere.

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 limit, format, and story_id are all documented in the input schema and the baseline is 3. The description adds only the ordering hint ('best sources first') and the earliest-articles note, giving no extra syntax or format guidance beyond the schema.

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 statement: 'Every article of one story (the coverage of one event) from search_news', and then enumerates exactly what comes back (newsroom count, first/last appearance, publisher, date, headline, link, earliest articles). It is clearly distinct from search_news because it takes a story_id produced by that sibling and expands a single story rather than searching.

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?

Three concrete usage contexts are given: gauging how big a story is, finding the original or most authoritative source, and collecting all coverage of an event. It also anchors the story_id parameter to a search_news result, which is the natural prerequisite. There is no explicit when-not guidance (e.g., use search_news instead when you don't already have a story id), so it stops short of a 5.

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