Skip to main content
Glama

SouthPow crypto & market data

buy_hn_bitcoin

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

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

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
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 it discloses the material behaviors: this is a paid call, the exact price ($0.002 USDC on Base), that no account or API key is needed, and the endpoint URL. It stops short of covering failure modes, caching, or rate limits, so it is strong but not exhaustive.

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?

Roughly three short sentences, front-loaded with the 'Paid.' flag before the resource description, then cost, auth, and endpoint. Every sentence carries distinct information (payment, content, pricing, auth, URL) with no filler.

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 two-optional-parameter read tool with no output schema, the description covers purpose, cost, auth requirements, ordering, and the shape of returned stories, which is enough for an agent to decide to call it. The only gaps are minor operational details such as failure/refund behavior on a paid call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so 'n' and 'sort' are already documented, giving a baseline of 3. The description adds meaning beyond the schema by stating the default ordering as 'newest first' and framing sort=top as the alternative, and by describing what each story contains (points, comments, links), which is output detail not present in the schema.

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 stories about 'bitcoin'), the ordering (newest first or sort=top), and the returned fields (points, comments, links), so an agent knows exactly what it gets. It never references the many siblings (buy_hn, buy_hn_crypto, buy_hn_ethereum) it sits beside, so the differentiation is inferred from the topic keyword rather than stated.

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?

Leading with 'Paid' and stating '$0.002 USDC on Base. No account, no API key' tells the agent this is a paid x402-style purchase with no signup prerequisite, which is useful invocation context. However, there is no explicit when-to-use vs when-not guidance, e.g. when to pick this over buy_hn or buy_hn_crypto, so the selection logic is only implied by the 'bitcoin' topic.

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