Skip to main content
Glama

aihot_get_story

Read-onlyIdempotent

Get the evolving timeline, latest development, AI digest, and related events for one public story. Only pass a public_id obtained from aihot_get_hot_topics storyPublicId; never invent or infer IDs.

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": {
      "public_id": "<public_id>"
    },
    "name": "aihot_get_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
public_idYesOpaque story public ID. Obtain it from aihot_get_hot_topics storyPublicId (or the final path segment of links.story); never guess it.
report_limitNoMaximum number of timeline reports, from 1 to 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / public_id / description
      Previous value: -"Opaque story public ID. Obtain it from the final path segment of aihot_get_hot_topics links.story; never guess it."New value: +"Opaque story public ID. Obtain it from aihot_get_hot_topics storyPublicId (or the final path segment of links.story); never guess it."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds the non-obvious ID-provenance constraint, which is real added value. However, it says nothing about how much history the timeline returns, whether results are truncated, or how report_limit interacts with completeness.

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?

Two sentences, front-loaded with what the tool returns, followed by the one constraint an agent could plausibly get wrong. No filler or restated naming.

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 usefully enumerates the return payload (timeline, latest development, digest, related events), which is the key completeness contribution. The main remaining gap is that it does not explain how many timeline entries are returned or what report_limit buys in practice.

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 coverage is 100%, with both public_id and report_limit fully documented including default and 1-50 range, so the schema carries the load. The description restates the provenance rule for public_id but adds nothing about report_limit. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb (Get) and enumerates the concrete payload for a single public story: evolving timeline, latest development, AI digest, and related events. That tells an agent this is a per-story detail lookup rather than a listing, which separates it from aihot_get_hot_topics. It stops short of contrasting with similar per-item siblings, so not a 5.

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?

It states a hard prerequisite: the ID must come from aihot_get_hot_topics storyPublicId, and must never be invented or inferred, which routes the agent to the discovery tool first. There is no explicit 'when not to use' or comparison against other detail-style siblings, so it falls 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.