Skip to main content
Glama

One news story in full

get_story
Read-onlyIdempotent

One news story (an event covered across outlets and days): summary, tone, timeline and every headline.

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": {
      "slug": "<slug>"
    },
    "name": "get_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesStory slug from search or get_company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description contributes beyond that by disclosing the shape of the returned content (summary, tone, timeline, every headline), which matters because no output schema exists. It does not mention error behavior for an unknown or stale slug.

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?

A single dense sentence that front-loads the resource and immediately follows with the returned fields. The parenthetical definition of "story" is the one piece of extra wording and it earns its place by disambiguating the concept.

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?

For a one-parameter lookup with no output schema, the description supplies the essential return-content picture and the domain definition of a story. The main gap is the upstream workflow (where a slug comes from) being relegated to the schema rather than stated in the description.

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?

With one parameter at 100% schema description coverage, the schema already explains that slug comes from search or get_company. The description adds nothing about slug format, case sensitivity, or how to recover from a bad slug, so the baseline 3 applies.

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

Purpose4/5

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

The description names a specific resource and defines it precisely ("an event covered across outlets and days"), then enumerates what is returned: summary, tone, timeline, every headline. This is clearly a single-story retrieval tool, distinguishable from search_news by the singular scope, though the description never explicitly contrasts the two.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers it should call this after finding a story via search_news or get_company, a flow hinted at only in the slug parameter's schema text ("Story slug from search or get_company"), not in the description. There is no explicit when-to-use or when-not guidance, and no exclusion of the sibling search tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources