Skip to main content
Glama
Sign In

cryptonews.is

by is.cryptonews
OverviewDiscussionsAdmin

Get story

get_story
Read-only

Standard and Pro: story detail and publisher reports, including archived stories. A story’s id can change once grouping settles, and old ids keep resolving to the current story: a merged id returns the current story with replaced_by (its id) and requested_id (the id you asked for); archived marks archived responses. During an upstream restart the story may come from a saved copy with stale:true and age. Story language identifies the copy (null means the copy is not written yet); copy_pending marks missing copy; copy_skipped: the story is rated negligible and will not get a summary (it is dropped if copy arrives later). The first 8 reports each carry the outlet’s own English headline and summary (null when none; report_copy.with_copy counts them). An id prefix of at least 8 characters resolves when unique (else 400 ambiguous_id with candidates). Cite stories by their full id or reader_url; ids are stable, and merged ids return replaced_by.

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

Input Schema

NameRequiredDescriptionDefault
idYes
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description goes far beyond them: merged ids return replaced_by and requested_id, archived responses are marked, upstream restarts can yield stale:true with age, and copy_pending/copy_skipped explain missing summaries. It also documents the failure mode (400 ambiguous_id with candidates) and the 8-report cap, which is substantial behavioral disclosure for a read tool.

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?

Wait—reassess: the opening sentence is front-loaded and useful, but the remainder is a dense, semicolon-chained block mixing id semantics, staleness, copy states, report fields, and citation advice with no paragraphing or ordering. Every fact earns its place given the absent output schema, but the structure makes it hard to scan. Score 3.

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 must explain return values, and it covers the important ones (replaced_by, requested_id, archived, stale/age, copy_pending, copy_skipped, report_copy.with_copy, reader_url). It falls short only on the language parameter's effect and on pagination or size limits for the reports list.

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 0%, so the description must carry parameter meaning. It does this well for 'id' (prefix-resolution rules, merged-id aliasing, full id vs reader_url for citation), but 'language' is only obliquely addressed via the phrase 'Story language identifies the copy,' which reads more like a response field than an explanation of what passing a language does.

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?

Opens with a concrete verb+resource statement: 'story detail and publisher reports, including archived stories,' scoped to Standard and Pro plans. It is clearly a by-id retrieval tool, distinct from siblings like search_stories and latest_stories, though it never names those siblings explicitly.

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?

Gives operational conditions (id prefixes of 8+ characters resolve when unique, otherwise 400 ambiguous_id with candidates; cite by full id or reader_url) that tell the agent how to call it successfully. However, it never says when to use this versus search_stories or latest_stories to obtain an id in the first place, so routing guidance is only implied.

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

All cryptonews.is toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources