Skip to main content
Glama

SouthPow crypto & market data

buy_hn_google

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

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries a heavy load, and it succeeds by providing critical behavioral information: the service is 'Paid', the cost ($0.002 USDC on Base), and technical requirements (No account, no API key).

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?

The description is highly efficient. It presents the core service, the technical payment/access constraints, and the URL in a dense but readable format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition is extremely complete for an AI agent. It covers what the tool does, how it is paid for, which assets are required, and provides the full service URL for direct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the input schema is comprehensive, the description provides semantic context by stating sorting options ('newest first' or 'sort=top') and providing the practical limit for the story count (1-30).

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?

The description clearly defines the tool's function: fetching Hacker News stories specifically related to 'google'. It distinguishes itself from the general 'buy_hn' sibling and other topic-specific tools by focusing on its subject matter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implicitly guided by the specific 'google' focus of the name and description, differentiating it from other tools in the 'buy_hn' family. It is clear that this is a specialized tool within a broader set of news fetching tools.

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