Genexxis paid agent tools (x402)

hn_hackernews

Hacker News stories: front-page lists (top, new, best, ask, show) or full-text search, each with title, URL, domain, points, comment count, author, time, HN link and text excerpt. Price: $0.005 USDC per call, paid with x402 on Base.

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_hackernews"
  }
}

Input Schema

Name	Required	Description
`q`	No	Search query (required for mode=search)
`days`	No	Search only: limit to stories from the last N days
`mode`	No	top \| new \| best \| ask \| show \| search (default top)
`sort`	No	Search only: relevance \| date (default relevance)
`tags`	No	Search only: story \| ask_hn \| show_hn \| front_page \| comment (default story)
`maxItems`	No	1-50, default 20

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden — and it discloses the single most decision-relevant trait: a paid call at $0.005 USDC per call via x402 on Base. That is real value beyond structured fields. It stops short of noting rate limits, failure modes, or pagination behavior across the maxItems cap.

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?

Two sentences, no filler, with the core capability front-loaded and the payment constraint appended second. Every clause earns its place.

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 six-parameter, no-output-schema tool, the description covers what it returns (title, URL, domain, points, comments, author, time, HN link, excerpt) and the cost barrier, which is what an agent needs to decide and pay. Missing only edge behavior such as result caps or empty-result handling.

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%, so every parameter is already documented, including mode values and search-only scoping for q/days/sort/tags. The description only restates the mode vocabulary and adds no syntax or format detail (e.g., how days is counted). Baseline 3 is appropriate.

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?

States a specific resource (Hacker News stories) plus its two access modes (front-page lists: top/new/best/ask/show, or full-text search) and enumerates the returned fields. It is clear enough to separate it from hn_item and hn_user by resource scope, but never names those siblings explicitly to reinforce the boundary.

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?

Implies usage via the mode list ('front-page lists ... or full-text search'), so an agent can infer that search requires q while listing does not. There is no explicit when-to-use guidance, no mention of hn_item/hn_user as alternatives, and no stated prerequisites beyond the payment note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Genexxis paid agent tools (x402) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?