Skip to main content
Glama

SouthPow crypto & market data

buy_coin_WHUF

Paid. WHUF/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/WHUF.

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

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 burden and does substantial work: it discloses the price ($0.10 USDC on Base), that no account or API key is needed, that failed calls are not charged, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It omits rate limits, retry behavior, and how the payment is actually negotiated.

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?

Six short fragments, front-loaded with 'Paid' and the data payload before pricing and logistics. Nothing is redundant and each clause (cost, auth, failure policy, sources, URL) adds distinct decision-relevant information.

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 tool with no output schema, the description compensates well by listing the exact returned metrics and naming the data sources. The remaining gap is the mechanics of the paid call — how the $0.10 USDC payment on Base is presented to the endpoint — which is not explained.

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 and the schema is empty, so there is no parameter meaning to add; baseline 4 applies. The description usefully confirms the call is fully determined by the endpoint URL, so the agent knows nothing needs to be supplied.

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 (WHUF/USD) and enumerates the returned fields: last price, 24h open/high/low, percent change, 24h and 30d volume. That is a specific verb-plus-resource statement an agent can act on. It does not distinguish itself from the generic sibling buy_crypto_price, which is the only missing differentiation.

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 by the symbol-specific name and the 'live' framing, but the description never states when to prefer this over buy_crypto_price or any other price sibling, nor any when-not condition. An agent must infer that this tool is the WHUF-specific variant.

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