Skip to main content
Glama

SouthPow crypto & market data

buy_coin_HNT

Paid. HNT/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.002 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/HNT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the full burden and does well: it discloses that calls are paid ($0.002 USDC on Base), require no account or API key, are not charged on failure, and that data is sourced from Coinbase Exchange with a Kraken cross-check. It does not mention rate limits, latency/freshness, or the response shape, which keeps it from a 5 given there is no output schema.

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?

Information is front-loaded (cost first, then payload, then terms, then endpoint) and every clause carries content. The telegraphic fragment style ('Paid.', 'No account, no API key.') is dense but slightly clipped, which is the only thing keeping it below a 5.

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 zero-parameter paid data endpoint with no output schema, the description covers cost, auth, failure billing, data sources, returned fields, and the underlying URL. The remaining gap is data freshness and response format details, which an agent may want before relying on the values.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly adds no parameter narrative and instead spends its words on what the call returns and costs. Nothing about invocation is ambiguous.

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 a specific resource (HNT/USD) and enumerates exactly what comes back: last price, 24h open/high/low, % change, 24h and 30d volume. The verb is only implied ('live' data returned) and the 'buy' framing in the tool name is left to be reconciled with 'Paid. $0.002 USDC', but an agent can still tell what this tool yields without opening a schema. Sibling differentiation is inherent since each buy_coin_* covers a distinct ticker.

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: call this to get HNT/USD spot and volume data. The cost and no-account details help the agent decide whether calling is acceptable, but there is no explicit when-to-use or when-not guidance, and the generic sibling buy_crypto_price is never referenced as the alternative for other tickers or multi-coin queries.

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