Skip to main content
Glama

SouthPow crypto & market data

buy_hn_ask-hn

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

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_ask-hn"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 burden and does well: it discloses that the call is paid ($0.10 USDC on Base), requires no account or API key, returns points/comments/links, and defaults to newest-first. Gaps remain around the payment mechanics (what happens on failed or refused payment) and any rate limits, which is why it is not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and compact: payment status first, then the resource, then cost/auth/endpoint, with no filler sentences. The telegraphic style and the trailing raw URL are slightly abrupt but each fragment carries information an agent needs.

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-parameter, no-output-schema read tool, the description covers content, ordering, returned fields, price, and auth model, which is most of what an agent needs. Only the payment flow and failure behavior are left unstated.

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% and both parameters are documented there, so the baseline is 3. The description restates the sort behavior ("newest first (or sort=top)") without adding format or edge-case detail, and never mentions the n parameter's 1-30 range.

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?

"Hacker News stories about 'ask hn'" names a specific resource and topic, which cleanly separates it from siblings such as buy_hn_show-hn and the generic buy_hn. There is no explicit verb ("Paid." is a marker, not an action), but the tool name plus the resource statement make the operation unambiguous.

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 only implied by the topic label; there is no statement of when to pick this over buy_hn (general feed) or buy_hn_show-hn, nor any exclusion or prerequisite guidance. The cost line ("$0.10 USDC on Base") does give an agent the key decision input about spending, which lifts it above pure silence.

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