Skip to main content
Glama

FoxAPIs data sources

Hacker News post

hackernews_post
Read-onlyIdempotent

A Hacker News story: title, link, points, comment count, author and posting time, from its item link. Costs 1 credit 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_post"
  }
}

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.6/5.0
Behavior4/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 genuinely new operational context: 1 credit per call, no charge when no data is returned, and a required FoxAPIs key. It does not describe failure modes for malformed or non-HN URLs, which keeps it short of a 5.

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?

A single dense sentence front-loads the returned fields, then appends cost and auth notes. Nothing is wasted, though the trailing cost/key clauses make it slightly cluttered and 'from its item link' is a touch awkward.

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

Completeness3/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 correctly enumerates the return fields, and it covers cost and auth. It is still thin on what happens with an invalid or non-HN URL and on whether comment text is included, which matters for a one-parameter lookup tool.

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% and the single url parameter already carries an example, so the schema does the heavy lifting. The description only reinforces that the URL must be the item link, adding little beyond the structured field — the 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?

The description names the resource (a Hacker News story) and enumerates exactly what is returned: title, link, points, comment count, author and posting time, plus the input it derives from (the item link). That is specific enough to separate it from hackernews_comments, though it never uses an explicit verb like 'fetch' and does not name the sibling it differs from.

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: you supply an HN item link and get story metadata back. There is no statement of when to prefer this over hackernews_comments or other post tools, and no exclusions or prerequisites beyond the API key note.

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