Skip to main content
Glama

IKANGAI AI News

Read an AI news story

get_story
Read-onlyIdempotent

One full article by its id, with its timeline, original sources and further reporting.

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
idYesA story id from the other tools, or the story's URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds value by saying what the response bundles (timeline, original sources, further reporting), but says nothing about behavior for an unknown/expired id, response size, or whether the article is complete vs. truncated.

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 front-loaded sentence with no filler; the payload contents are listed compactly after the core purpose. Nothing could be removed without losing information.

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 simple single-record read with one fully documented parameter and complete annotations, this is close to sufficient — the agent knows what it gets back and that it is a safe, idempotent read. The only shortfall is absent guidance on linking it to the list/search siblings or handling a bad id.

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?

There is a single parameter at 100% schema description coverage, where the schema itself explains that the id may be 'a story id from the other tools, or the story's URL'. The description's 'by its id' merely restates this and adds no format, validation, or URL-acceptance detail of its own.

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 the resource (one full article) and the selector (by its id), and enumerates what the payload contains: timeline, original sources, further reporting. That distinguishes it from the list-style siblings (latest_stories, search_stories) by implication, though no sibling is named 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?

Usage is only implied: retrieval 'by its id' suggests a detail call after a list or search, but the description never states when to prefer this over search_stories or latest_stories, nor any preconditions. The workflow hint (id comes from other tools) lives in the schema parameter text rather than the description.

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