Skip to main content
Glama

SouthPow crypto & market data

buy_coin_HOPR

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 burden well: it discloses that the call is paid, the exact price ($0.10 USDC on Base), that no account or API key is needed, and that failed calls are not charged. It stops short of latency, rate limits, or retry behavior, but the payment/auth/failure profile is unusually well covered.

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 dense and front-loaded: payload fields first, then data sources, then cost/payment, then the endpoint URL. The telegraphic fragments are efficient but slightly reduce readability, and 'Paid.' followed later by the actual price is mildly redundant.

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?

For a zero-parameter paid data lookup with no output schema, the description supplies everything needed: the returned fields, the upstream sources (Coinbase Exchange with Kraken cross-check), the payment terms, and the endpoint. An agent can decide and invoke without further information.

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 there is nothing to disambiguate and the baseline of 4 applies. The description correctly requires no caller input; the URL is a fixed endpoint, not a parameter.

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 exact resource (HOPR/USD) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. It is unambiguous which sibling token tool it belongs to and what it delivers, though it leads with a fragment ('Paid.') rather than a verb like 'Get HOPR/USD price'.

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

Usage Guidelines2/5

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

No guidance on when to choose this over buy_crypto_price or the other buy_coin_* siblings, and no when-not conditions. The only usage-relevant signals are cost and the absence of an account/API-key requirement, which are stated as facts rather than selection criteria.

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