Skip to main content
Glama

SouthPow crypto & market data

buy_hn_kubernetes

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

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

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 full load and does well: it discloses that invoking costs $0.01 USDC on Base and needs no account or API key, which is the key behavioral fact for a paid endpoint. It omits failure behavior (what happens on an unpaid or rejected payment) and whether results are paginated, keeping it short of 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.

Conciseness5/5

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

Four terse fragments, front-loaded with the paid flag and the resource, with zero filler. Every clause adds a distinct fact: topic, ordering, return fields, price, and the endpoint URL.

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-param read tool with no output schema, the description covers topic, ordering, returned fields, payment requirements, and even the raw URL, which is enough to call it correctly. The only real gap is payment-failure and retry semantics, which an agent handling a paid endpoint would want to know.

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 both parameters are already documented with defaults and allowed values. The description echoes the sort behavior ("newest first (or sort=top)") but adds no syntax, range, or interaction detail beyond the schema, so the baseline applies.

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?

"Hacker News stories about 'kubernetes', newest first (or sort=top), with points, comments and links" names a specific resource, its topic filter, its ordering, and its returned fields. The topic suffix in the name plus this sentence makes it unambiguously distinct from the other buy_hn_* siblings.

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?

It states the tool is paid and gives the price and chain, which frames when the call is appropriate, and the topic is implied by the name. However it never says when to prefer a sibling (e.g. general buy_hn for unfiltered stories, or another topic variant) or whether a prior balance/approval step is needed, so routing is inferred rather than stated.

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