Skip to main content
Glama

SouthPow crypto & market data

buy_coin_HBAR

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 behavioral burden and does so well: it discloses the paid/toll model, the exact cost and network, the no-auth requirement, and the no-charge-on-failure policy. It stops short of explaining the payment flow or rate limits, but the economic and auth behavior is unusually complete.

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?

A single dense sentence group with zero filler; the payment terms and the endpoint URL are front-loaded. Every clause (cost, auth, failure policy, data sources) carries information an agent needs before calling.

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-param, no-output-schema pricing tool, the description supplies the return fields, the vendor sources, the cost, and the endpoint. The only missing piece is how payment is actually transacted (the $0.05 USDC handshake), which an agent might need to invoke it end-to-end.

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 for the schema to describe and no semantic gap to fill. The description's enumeration of returned fields substitutes usefully for the absent output schema.

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 (HBAR/USD live price with 24h open/high/low, % change, 24h and 30d volume) and cites the data sources. It is distinguishable from siblings only via the ticker in the name rather than the description itself, but the payload 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?

It states the access conditions clearly (paid, $0.05 USDC on Base, no account or API key, failed calls not charged), which is useful pre-call context. It never says when to prefer this over alternatives like buy_crypto_price or explains what a caller does with the payment URL, so selection guidance is only implied.

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