Skip to main content
Glama

SouthPow crypto & market data

buy_hn_apple

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

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does disclose the paid model, exact cost, chain, and that no account or API key is needed, plus the returned fields, but it says nothing about what happens on payment failure, refunds, rate limits, or result freshness — the main behavioral risks of 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?

Compact and front-loaded: 'Paid.' flags the key constraint immediately, then purpose, then pricing and access details, then the endpoint URL. The telegraphic fragment style leaves a few items (price, chain) loosely stacked, but nothing is redundant.

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, no-required-input tool with no output schema, it covers what the agent most needs: that calling it costs money, how to pay, and what the response contains. Remaining gaps are edge behavior on failed payment and error/rate-limit handling.

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 and sort. The description adds a little meaning by restating the default ordering (newest first) and confirming the top-sort alternative, but adds nothing about the 1-30 range or default count that the schema does not already cover.

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 (Hacker News stories about 'apple'), the ordering (newest first, or sort=top), and the payload returned (points, comments, links). The topic-specific scope implicitly separates it from the many sibling buy_hn_<topic> feeds and the generic buy_hn, though no sibling is named explicitly.

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 the prerequisites for calling it (paid, $0.25 USDC on Base, no account or API key), which is useful context, but never says when to prefer this feed over the generic buy_hn or another topic feed. Usage is only implied by the topic name in the description.

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