Skip to main content
Glama

SouthPow crypto & market data

buy_hn_climate

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

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

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 the price ($0.25 USDC on Base), that no account or API key is needed, the endpoint URL, and the fields returned. It stops short of explaining payment mechanics (e.g., how the USDC charge is settled), failure/refund behavior, or 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?

Two compact sentences with the most decision-relevant fact ('Paid') front-loaded, followed by content, ordering, return fields, payment, and endpoint — 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 zero-required-parameter paid fetch tool with no output schema, the description covers cost, auth model, ordering, and returned fields, which is nearly everything needed. Only the response envelope/format and error behavior are left unstated, and those are minor here.

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 with defaults and ranges. The description only echoes the sort default and the 'top' alternative, adding marginal meaning beyond the schema, which is the baseline case.

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 the exact resource and topic scope ('Hacker News stories about climate') plus the ordering and returned fields (points, comments, links), which separates it from the generic buy_hn and from the other topic-specific buy_hn_* siblings without opening any schema.

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' prefix and the '(or sort=top)' note give the agent enough to know this is a paid retrieval call and how to choose ordering, but there is no explicit when-to-use versus buy_hn or a sibling topic feed, and no stated exclusions or preconditions.

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