Skip to main content
Glama

Hacker News top stories (x402)

hn_top_stories

Read-onlyIdempotent

$0.09 via x402: Hacker News top stories with score, author, comment count and links. Live.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hn_top_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo1-20
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful context beyond them: a concrete price ($0.09 via x402) and a 'Live' freshness claim. It stops short of describing result count, pagination, or what happens when payment terms are returned, which for a paid call would be valuable.

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 compact sentence plus price prefix, with no filler. The cost is front-loaded, which is arguably appropriate for a paid call, though placing the resource first would read slightly better for tool selection.

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, the description carries the burden of stating returns, and it does so by naming the included fields. Combined with the schema documenting the 1-20 count and the payment flow, an agent has enough to call it correctly; only rate limits and response shape details are absent.

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 description coverage is 100%, and both parameters ('top' with range 1-20 and 'x_payment' with its omit-to-get-terms instruction) are documented in the schema itself. The description adds no meaning beyond that, 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 (Hacker News top stories) and enumerates the returned fields (score, author, comment count, links), so an agent knows exactly what data comes back. The verb is implicit ('top stories' as a listing) and there is no explicit differentiation from similar siblings like github_trending or papers_latest, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no when-to-use or when-not-to-use guidance and names no alternative tool. The word 'Live' hints at real-time freshness, but nothing tells an agent when this source should be preferred over web_search or the other content-fetching siblings.

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