Skip to main content
Glama

FoxAPIs data sources

Show HN post outcome

showhn_post_outcome
Read-onlyIdempotent

How one Show HN post did: points, comments, when it was posted and its rank among all Show HN posts we hold. 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": {
      "hn_id": "<hn_id>"
    },
    "name": "showhn_post_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
hn_idYesThe Hacker News item id, or its news.ycombinator.com/item?id= address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuinely useful context beyond them: a 1-credit cost per call, no charge for empty answers, and an API key requirement.

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?

Three short clauses: what it returns, what it costs, what it needs. Front-loaded with the outcome metrics and no filler, though the phrasing 'we hold' is slightly vague.

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, no-output-schema tool, the description supplies the return fields, billing rules, and auth requirement, which is nearly everything an agent needs. Only minor gaps remain, such as what an empty/no-data answer looks like.

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 hn_id parameter already documents that it accepts either an item id or a news.ycombinator.com item URL. The description adds nothing further about the parameter, so 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 a specific resource (one Show HN post) and enumerates the returned dimensions: points, comments, posting time, and rank among stored Show HN posts. That is clearly distinct from a timing/advice sibling like showhn_best_time, though it does not name any alternative explicitly.

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 implied rather than stated: you call it when you have an HN item id and want that post's performance. There is no explicit when-not guidance or named alternative, but the cost and key requirements give practical context for deciding to call.

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