Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SAND

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

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

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 the price ($0.10 USDC on Base), the payment rail, that no account or API key is required, that failed calls are not charged, and the upstream data sources including a Kraken cross-check. What it omits is the mechanics of the payment handshake and the response format/latency, which matters for a metered endpoint.

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?

It is a dense, front-loaded block: cost and payment first, then data content, then access terms, then URL. Every clause is substantive, though the telegraphic style (sentence fragments, 'Paid.') is terse enough that a first-time agent may need a pass to parse the payment prerequisite.

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?

There is no output schema, so the description must convey return values, and it does by enumerating the price fields. For a zero-parameter, paid data fetch the essential details — cost, currency, chain, auth exemption, failure billing, data provenance, endpoint — are all present; only the exact response shape and payment protocol steps are left implicit.

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 no parameter semantics to explain and the baseline is 4. The description appropriately spends its words on output content and payment terms instead of inventing parameters.

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 specific resource (SAND/USD) and enumerates exactly what is returned: last price, 24h open/high/low, percent change, and 24h/30d volume. It is clearly a paid market-data endpoint rather than a trade executor, which is useful given the 'buy_coin_' naming family. It does not explicitly differentiate itself from the generic sibling buy_crypto_price, which keeps it below a 5.

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 only implied: an agent infers it should call this when it needs SAND spot data. There is no explicit statement of when to prefer this over buy_crypto_price or the other buy_coin_* variants, and no when-not-to guidance. The purchasing preconditions (no account, no API key) are present, which is helpful context but not selection guidance.

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