Skip to main content
Glama

hn_story

Read-only

Retrieve a single Hacker News story by item ID to get its title, author, score, link, text, and comment count.

Instructions

Get one Hacker News story by id: title, author, score, link, text and comment count.

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": "hn_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesHacker News item id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-dependency behavior are covered structurally. The description adds useful context by listing exactly which fields come back, which compensates for the absent output schema, but it says nothing about failure behavior for invalid, deleted, or non-story ids.

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 sentence, front-loaded with the verb and resource, and every clause (id key, returned fields) carries information. No padding or redundant restatement of the tool name.

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 read tool with no output schema, the description supplies the return field list and the access key, which is most of what an agent needs. The only meaningful omission is behavior on missing or non-story ids.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter exists and the schema already documents it fully at 100% coverage as a 'Hacker News item id' with bounds. The description reinforces that the value is a story id, though it adds no format hints such as where an id can be found.

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?

States a specific verb ("Get") plus resource ("Hacker News story") and adds the retrieval key ("by id"), which naturally separates it from the sibling search tool without naming it. The enumerated return fields further pin down what kind of resource this is.

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: 'by id' signals single-item lookup versus a search-style sibling, but the description never states when to prefer this over hn_search or what to do if only a title is known. Adequate for a trivial one-parameter lookup but with a clear gap.

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

Deploy Server

Other Tools