Skip to main content
Glama

SouthPow crypto & market data

buy_hn_space

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

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

Input Schema

NameRequiredDescriptionDefault
nNoStories, 1-30 (default 10)
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 supplied, the description carries the full burden and does a fair job: it discloses that the call is paid, the exact price and currency/chain, that no auth is needed, and the endpoint URL. It omits failure behavior (what happens if payment fails or is insufficient) and any rate limit or per-call billing semantics, which for a paid tool would be valuable.

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-loads the most decision-relevant fact ('Paid.') and packs scope, output fields, price, auth requirements and URL into a few tight fragments with no filler. The telegraphic style is efficient, though slightly fragmented.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read tool with no output schema, the description covers what the tool returns (stories with points, comments, links), default ordering, cost, and access method. There is no output schema to explain, and the essentials an agent needs before calling are present.

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%, so the schema already documents both n (1-30, default 10) and sort (recent/top). The description only restates the default ordering and mentions sort=top, adding no syntax or behavior beyond the schema, so the baseline 3 applies.

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?

States a concrete resource and scope: Hacker News stories about 'space', newest first by default, returning points, comments and links. The topic qualifier distinguishes it from the general buy_hn sibling, but it never names buy_hn or the other topic variants, so an agent must infer the routing from the name alone.

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 gives useful preconditions for use (paid, $0.10 USDC on Base, no account or API key required), which tells an agent it can call this without setup. However, there is no explicit when-to-use vs when-not guidance and no mention of the alternative topic-specific or general HN tools in the sibling set.

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