Skip to main content
Glama

FoxAPIs data sources

Hacker News comments

hackernews_comments
Read-onlyIdempotent

The comment thread under a Hacker News item: top comments with authors and scores. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "url": "<url>"
    },
    "name": "hackernews_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://news.ycombinator.com/item?id=8863"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), and the description adds real operational context beyond them: 2 credits per call, no charge for an empty answer, and a FoxAPIs key requirement. It still doesn't say how many comments are returned or how ordering/pagination works, keeping it short of full transparency.

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?

Three short sentences, front-loaded with what the tool returns and followed by cost and auth requirements. Every sentence carries information an agent would act on, with no filler.

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 and a single parameter, the description adequately covers what comes back (top comments with authors and scores), the cost model, and the auth requirement. The only gap is ranking/pagination or result-count expectations, which is minor for this complexity.

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 one parameter with 100% schema coverage, so the schema already documents the url. The description only implies that the url points at a Hacker News item thread, adding little format or validation meaning beyond what the schema example provides; baseline 3 applies.

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?

Names a specific resource (the comment thread under a Hacker News item) and states what it returns (top comments with authors and scores), which goes beyond restating the name. It does not explicitly distinguish itself from the sibling hackernews_post, so an agent must infer that this tool is for the thread rather than the item itself.

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: the required url parameter and the 'under a Hacker News item' phrasing hint that this is called after identifying an item. There is no explicit when-to-use/when-not guidance and no named alternative, though the credit-cost note gives useful invocation context.

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