Skip to main content
Glama

Hacker News thread

hackernews_thread
Read-only

Hacker News Comments & Threads: one Hacker News story or comment by id or news.ycombinator.com URL with its direct replies (up to 8 per call, next_cursor for more), deleted and dead replies skipped. Per item the text as plain text, author, score, reply count, parent and time in the shared social schema. Bad input is free; not found or no match is not charged. Price: $0.01 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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

Input Schema

NameRequiredDescriptionDefault
idYesThe story or comment: a Hacker News item id (a positive whole number) or a news.ycombinator.com/item?id= URL.
limitNoDirect replies wanted, 1-50 (default 10); one call returns at most 8, next_cursor pages through the rest.
cursorNonext_cursor of the previous page (a reply offset).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that deleted and dead replies are skipped, that at most 8 replies return per call with next_cursor paging, the exact per-item fields returned, and the charging model (bad input free, not-found free, $0.01 per successful call via x402 payment in _meta). These are the operational facts an agent cannot infer from readOnlyHint/openWorldHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads identity and scope, then behavior, then pricing — a sensible order for an agent. It stays compact despite covering a lot, though the payment sentence is dense and the 'shared social schema' reference is left unexplained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema available, the description still enumerates the returned fields (text as plain text, author, score, reply count, parent, time) and covers pagination, skipped content, and payment requirements. An agent has everything needed to call it and interpret the result.

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%, so every parameter is already documented. The description restates the 8-per-call cap and cursor paging, which reinforces the limit-vs-page-size distinction but adds little that the schema doesn't already say.

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

Purpose5/5

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

States a specific verb and resource: fetch 'one Hacker News story or comment by id or news.ycombinator.com URL' together with its direct replies. The singular-item scope clearly separates it from hackernews_search, which presumably finds items without a known id.

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?

The description makes clear this is for a single known item id or URL, which implicitly routes multi-item discovery to hackernews_search. It doesn't explicitly name the alternative or state exclusions, so it stops short of a full when/when-not statement.

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.