Skip to main content
Glama

SouthPow crypto & market data

buy_hn_startups

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

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

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 meaningful work: it discloses that the call is paid ($0.05 USDC on Base) and that no account or API key is required, which is critical for an agent deciding whether it can even invoke it. It omits edge behavior such as whether payment is per-call or per-retry, but the core cost/auth model is stated.

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?

Two compact sentences, front-loaded with the cost flag and then the resource, with no filler. The trailing documentation URL is useful rather than wasteful.

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-parameter read tool with full schema coverage and no output schema, the description covers topic, ordering, returned fields, price, and auth requirements. Remaining gaps (pagination, per-call billing semantics) are minor at this complexity level.

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 adds only that results are 'newest first (or sort=top)', which lightly clarifies the sort values but goes no further than the schema; the 'n' parameter is not mentioned at all. 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 specific verb+resource: Hacker News stories about the topic 'startups', with the returned fields (points, comments, links) and default ordering. It is distinguishable from siblings like buy_hn (general) or buy_hn_openai (other topic) by the named topic, though it never explicitly contrasts with them.

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 explicit statement like 'use buy_hn for general HN queries' or a condition that would select this over the other topic-scoped HN siblings. The 'Paid.' prefix and price at least signal the cost trade-off before invoking.

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