Skip to main content
Glama

SouthPow crypto & market data

buy_hn

Paid. Hacker News search: stories matching a keyword, newest first or top-voted, with points, comment count and links. $0.003 USDC on Base. No account, no API key. URL https://southpow.media/v1/hn.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "buy_hn"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoStories, 1-30 (default 10)
qYesKeyword, e.g. x402
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, the description carries the full behavior burden and does well: it discloses that the call is paid ($0.003 USDC on Base), that no account or API key is needed, and the endpoint URL. These are exactly the non-obvious traits an agent needs before invoking a paid tool. It stops short of rate limits, error/failure semantics, or what happens if payment is insufficient.

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 telegraphic sentences, front-loaded with 'Paid.' so the cost is the first thing seen, followed by what it does, then price, then access. Every clause carries information; no filler or marketing prose.

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 3-parameter search tool with no output schema and no annotations, the description covers purpose, payment model, access requirements, and the shape of a result (points, comment count, links). What remains missing is failure behavior and pagination/result-window semantics, which matters somewhat given the n cap of 30.

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 q, n and sort are already documented; baseline is 3. The description adds some value by naming the two sort modes ('newest first or top-voted') and the fields present in results, but it never mentions the n limit of 1-30, so it does not meaningfully extend 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 verb and resource: 'Hacker News search: stories matching a keyword', plus what each result carries (points, comment count, links). That clearly separates it from buy_crypto_price, buy_polymarket and buy_insider. It never addresses the generic sibling buy_search, so the boundary with that tool is left for the agent to infer.

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 is implied rather than stated: the agent can infer 'use this when you want HN stories about a keyword'. There is no explicit when-not-to-use, no mention of when buy_search or search_facts would be preferable, and no guidance on payment failure or retry. The 'no account, no API key' line removes an access precondition but does not route between tools.

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