Skip to main content
Glama

SouthPow crypto & market data

buy_hn_robotics

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

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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, the exact price, the payment network, and that no account or API key is needed. It stops short of explaining how payment is actually settled (pre-funded balance, per-call payment, failure behavior), which matters for a paid endpoint.

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 behavior, cost, auth, and endpoint URL into a compact block with no filler. The raw URL is slightly noisy but arguably useful for the agent.

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

Completeness3/5

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

No output schema exists, and the description does list the returned fields, which compensates. The gap is operational: for a paid tool, the payment flow and what happens on insufficient funds are left unexplained, and there is no indication of pagination or result freshness beyond 'newest first'.

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 both parameters are already documented. The description only adds the implication that 'newest first' is the default, which mildly reinforces the sort parameter; n is not mentioned at all beyond 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?

States a specific resource (Hacker News stories on the 'robotics' topic) with the returned content (points, comments, links) and default ordering. It is distinguishable from the buy_hn_* topic siblings only via the topic term, but that is enough given the naming pattern.

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?

The 'Paid ... $0.05 USDC on Base. No account, no API key' line tells the agent prerequisites and cost, which is genuine usage context. However, it never says when to pick this over the generic buy_hn or other topic tools, and gives no guidance on when the spend is justified.

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