Skip to main content
Glama

SouthPow crypto & market data

buy_coin_HYPE

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

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

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 supplied, the description does solid work: it discloses the $0.25 USDC-on-Base cost, that no account or API key is required, that failed calls are not charged, and the underlying data sources (Coinbase Exchange with Kraken cross-check). Gaps remain around latency, output encoding, and whether a pre-funded wallet is required before the first call.

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?

One dense paragraph, front-loaded with cost and the primary payload, followed by payment mechanics and the endpoint URL. Every clause is informative; the only mild inefficiency is that the field list and the logistics run together without visual separation.

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-argument, no-annotations, no-output-schema tool, the description covers the important unknowns: what data comes back, what it costs, what credentials are needed, and the failure-charging policy. It could say more about the response format or rate limits, but nothing essential to a correct invocation is missing.

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 and there is no input semantics for the description to carry. The description correctly spends its words on payload content and payment terms instead of inventing parameter discussion.

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 resource precisely (HYPE/USD live price data) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. The 'Paid.' opener clarifies that the 'buy_' prefix means purchasing a data call, not buying the coin. It does not explicitly contrast itself with siblings like buy_crypto_price, but the HYPE-specific scope is unambiguous.

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 rather than stated: an agent can infer it should call this when it needs HYPE/USD market data. There is no explicit guidance on when to prefer this over buy_crypto_price or other price tools, and no mention of freshness semantics that would drive tool selection. Adequate but leaves the routing decision to inference.

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