Skip to main content
Glama

SouthPow crypto & market data

buy_hn_ethereum

Paid. Hacker News stories about 'ethereum', newest first (or sort=top), with points, comments and links. $0.01 USDC on Base. No account, no API key. URL https://southpow.media/v1/hn/ethereum.

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": "buy_hn_ethereum"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoStories, 1-30 (default 10)
sortNorecent (default) or top

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it discloses the paid model, exact price, payment chain, and absence of auth, plus the default ordering. It says nothing about how payment is executed (e.g., x402 flow), what happens on payment failure, or whether results are cached, which is a meaningful gap for a paid tool.

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?

Four short sentences, front-loaded with the 'Paid' flag and the payload summary, with no filler. Every sentence contributes either cost, prerequisites, content, or endpoint.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-param, no-required, read-only style tool with no output schema, the description covers what is returned (stories with points, comments, links), ordering, price, chain, and that no credentials are needed. That is sufficient for an agent to decide and call correctly.

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 are already documented there; the description only echoes the sort=top default via 'newest first (or sort=top)'. It adds no syntax, bounds, or interaction detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: Hacker News stories about 'ethereum', newest first by default, with points, comments and links. The topic-specific naming makes it trivially distinguishable from siblings like buy_hn_bitcoin or buy_hn_crypto.

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?

The cost line ($0.01 USDC on Base) and 'no account, no API key' tell an agent it must be willing to pay, which implicitly gates usage. However, it never says when to prefer this over the generic buy_hn or the broader buy_hn_crypto, and gives no guidance on when not to call it.

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