Skip to main content
Glama

SouthPow crypto & market data

buy_hn_nvidia

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

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

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 burden and does well: it discloses that the call is paid, the exact price ($0.01 USDC on Base), that no account or API key is needed, and what each result contains. It stops short of explaining how payment is actually settled (wallet flow, retries on failed payment) or any rate limits.

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?

Telegraphic and front-loaded: cost signal first, then what is returned, then payment/auth facts. Every clause (price, chain, no-API-key, endpoint URL) carries distinct information with no filler.

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-annotation, no-output-schema tool, the description covers the essentials an agent needs: topic, ordering, result fields, price, chain, and auth model. The one real gap is that the payment mechanism behind the $0.01 charge is never described, which matters for an agent deciding whether it can execute the call.

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 `n` and `sort` are already fully documented, and the baseline is 3. The description only restates the default ordering and the 'top' option, adding no new meaning such as how sorting interacts with the 1-30 count limit.

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?

Names a specific resource and scope: Hacker News stories about 'nvidia', newest-first with an optional top sort, returning points, comments and links. This clearly separates it from topic siblings like buy_hn_llm, buy_hn_ai-agents, or the generic buy_hn.

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 fixed topic — an agent must infer that this is the tool for Nvidia-related HN discussion rather than general HN (buy_hn) or adjacent topics. There is no explicit when-to-use statement, no exclusion naming a sibling, and no note about what happens if the topic yields few stories.

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