Skip to main content
Glama

SouthPow crypto & market data

buy_hn_crypto

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

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses that the call is paid, the exact price, the payment rail, and that no authentication is required, plus the endpoint URL. What it omits is how payment is actually transacted (e.g., x402 handshake), rate limits, and error behavior on failed payment.

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?

Three terse sentences, with the most decision-critical fact ('Paid.') front-loaded, followed by content, price/auth, and endpoint. No filler or repetition.

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 simple two-optional-parameter fetch with no output schema, the description covers content, sort behavior, returned fields, cost, and auth posture. The remaining gap is the mechanics of paying, which matters given the tool is explicitly paid.

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%, so the schema already documents both optional parameters, making 3 the baseline. The description adds only that results are 'newest first (or sort=top)', which mildly reinforces the sort default but adds little beyond the schema's 'recent (default) or top'.

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 gives a specific verb and resource: 'Hacker News stories about crypto', and states what each story carries (points, comments, links). This is clearly distinguishable from generic buy_hn or coin-price siblings by topic, though it never explicitly names an alternative.

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 context is implied through the paid framing ($0.05 USDC on Base, no account/API key), which tells the agent this is a pay-per-call data fetch. However, there is no explicit statement of when to pick this over buy_hn (general HN) or buy_pm_crypto, and no guidance on failure or retry situations.

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