Skip to main content
Glama

SouthPow crypto & market data

buy_hn_anthropic

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

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the behavioral burden. It usefully discloses cost ($0.10 USDC on Base), access model, ordering, and return fields, but omits payment mechanics, failure behavior, and refresh/caching details.

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?

The description is one compact, front-loaded block: payment status and cost first, then content, access terms, and endpoint. Every sentence earns its place 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 low-complexity paid feed with complete parameter descriptions and no output schema, the description provides enough to invoke it: topic, cost, auth model, ordering, and return fields. Payment execution details are omitted but likely outside the parameter surface.

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 corroborates the sort option ('newest first (or sort=top)') but adds no constraints or format details beyond the schema; baseline 3 is appropriate.

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?

The description identifies the resource precisely: Hacker News stories about 'anthropic', with ordering options and returned fields. That clearly distinguishes it from sibling topic feeds such as buy_hn_openai and buy_hn_llm, though it lacks an explicit verb like 'fetch' or 'buy'.

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 discloses that the call is paid and requires no account or API key, which helps an agent judge feasibility. However, it gives no explicit when-to-use or when-not guidance and does not name an alternative such as the generic buy_hn feed.

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