Skip to main content
Glama

SouthPow crypto & market data

buy_hn_llm

Paid. Hacker News stories about 'llm', 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/llm.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses cost ($0.01 USDC on Base), that no account or API key is required, the endpoints, and the fields returned (points, comments, links). It omits how the payment is actually executed and any error or rate-limit behavior, so it stops short of full disclosure.

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 short sentences, front-loaded with 'Paid.' so the agent sees the cost model immediately, then scope, then pricing/auth, then endpoint. No wasted wording.

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 read tool with no output schema and no annotations, the description covers cost, authentication, ordering, returned fields and the endpoint URL. The remaining gap is the mechanics of paying (wallet vs pre-funded balance), which matters for actually invoking a paid tool.

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 documented there, so the baseline applies. The description echoes the sort behavior ('newest first (or sort=top)') and default ordering but adds no syntax, unit or constraint 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?

Names a specific resource and topic: 'Hacker News stories about 'llm''. This distinguishes it from topic siblings like buy_hn_openai and buy_hn_ai-agents, and from the buy_coin_* family, without needing to open any schema.

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?

Implies when to use it (you want HN stories on 'llm', optionally sorted by top) and states the ordering options. However it never names an alternative tool or says when a different topic tool would be better (e.g. buy_hn_ai-agents or buy_hn_openai for adjacent coverage), leaving routing to inference.

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