Skip to main content
Glama

SouthPow crypto & market data

buy_hn_privacy

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

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

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 well: it discloses that the call is paid, the exact price ($0.25 USDC on Base), that no account or API key is needed, and the endpoint URL. It does not cover failure/payment-error behavior or rate limits, which keeps it below a 5.

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-loaded with 'Paid.' so the cost constraint is impossible to miss, then the resource, then price/auth/URL in a compact sequence. The telegraphic style is dense but every clause carries information; the bare URL is the only marginal element.

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 no output schema and no annotations, the description supplies the payment model, auth requirements, returned fields, and ordering. What remains thin is response shape detail and error/payment-failure handling, which is a modest gap given the tool's simplicity.

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 description coverage is 100%, with both 'n' (1-30, default 10) and 'sort' (recent/top) documented in the schema. The description only echoes the sort behavior ('newest first (or sort=top)') and says nothing about 'n', so it adds little 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 about 'privacy'), the ordering, and the fields returned (points, comments, links). It is clearly distinguishable from the sibling topic feeds like buy_hn_security or buy_hn_open-source, though it never explicitly contrasts itself 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?

Topic-specific usage is implied by the resource description, but there is no explicit when-to-use guidance versus the generic buy_hn or adjacent topic feeds, and no exclusions or prerequisites beyond the payment note.

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