Skip to main content
Glama

SouthPow crypto & market data

buy_hn_openai

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

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

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 cost ($0.05 USDC on Base), that no account or API key is required, the default sort order, and what each item contains (points, comments, links). It omits failure behaviour, whether the URL is a pay-per-call endpoint contract, and any 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero filler, and the most decision-relevant fact ('Paid') plus the price are front-loaded before the content description. The endpoint URL is placed last where it belongs.

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, the description covers content, ordering, item fields, cost, authentication burden and the endpoint, which is nearly everything an agent needs. Minor gaps remain around pagination and failure handling, but nothing essential to calling it correctly is missing.

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% and both parameters are optional, so the schema already documents 'n' (1-30, default 10) and 'sort' (recent or top). The description only restates the default ordering ('newest first (or sort=top)'), adding marginal meaning beyond the schema; baseline 3 applies.

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?

States a specific resource and filter: Hacker News stories about 'openai', newest first or top-sorted, with points, comments and links. The topic suffix plus the explicit ordering tells an agent exactly how this differs from the other buy_hn_* and buy_pm_openai siblings.

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 implied by the topic-specific naming and the 'Paid' framing, so an agent can infer this is the openai-flavoured HN feed rather than buy_hn or buy_pm_openai. However, there is no explicit statement of when to choose this over those alternatives, nor any exclusion or prerequisite guidance.

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