Skip to main content
Glama

SouthPow crypto & market data

buy_hn_ai-agents

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

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_ai-agents"
  }
}

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 supplied, the description carries the full disclosure burden and does well: it flags that the call is paid, quotes the exact price ($0.002 USDC on Base), and states no account or API key is required — all behaviour an agent cannot infer from the schema. It is silent on what happens if payment fails or whether the charge is per-call, 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?

Very short and front-loaded with the most decision-critical fact ('Paid'), followed by content, price and access details. The telegraphic phrasing ('Paid.') and trailing bare URL are efficient, though the fragments read more like an ad than structured guidance.

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 paid feed tool with no annotations and no output schema, the description covers cost, access requirements and the shape of returned items. Only error/payment-failure behaviour is unaddressed, which is a minor 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 coverage is 100%, so both parameters are already documented in the input schema; the description only echoes the sort choice ('newest first (or sort=top)'). It adds no extra meaning about the range or cost implications of 'n', so the baseline of 3 applies.

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 names the concrete resource (Hacker News stories tagged 'ai agents') and what each item carries (points, comments, links), which is enough to distinguish it from most siblings in the buy_hn_* family. It stops short of explicitly separating this topic from near-neighbours like buy_hn_llm or buy_hn_openai, and the listing verb is only implied by 'newest first'.

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 implies usage ('Paid', price, no account or API key needed) but never states when an agent should choose this over buy_hn_llm, buy_hn_openai or the generic buy_hn. The sort hint gives mild operational guidance, but there are no explicit when-to-use or when-not conditions.

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