Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FIDA

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

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

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 present, the description carries the full burden and does reasonably well: it discloses the paid model, price and payment rail, that no account or API key is needed, that failed calls are not charged, and that prices come from Coinbase Exchange with a Kraken cross-check. It does not explain the payment handshake (e.g., x402 flow), latency, or whether the quoted URL is the callable endpoint or mere documentation.

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?

A single dense sentence-chain with the most important constraint ('Paid.') front-loaded, followed by data content, then cost/auth terms, then the URL. Nothing is redundant, though the telegraphed fragments and trailing bare URL are slightly cryptic compared to a fully structured sentence.

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, zero-annotation price lookup with no output schema, the description covers what is returned, what it costs, what credentials are needed, data provenance, and failure billing. The only real gap is the ambiguity of the trailing URL and the absence of any note on payment mechanics.

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-level meaning to add; the baseline for a parameterless tool applies. The description does not waste space restating a schema that is empty.

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?

Names the exact resource (FIDA/USD) and enumerates the returned metrics: last price, 24h open/high/low, % change, 24h and 30d volume. The token-specific name plus the FIDA/USD phrasing makes the scope unambiguous against the hundreds of sibling buy_coin_* tools. It stops short of explicitly stating 'FIDA only — use buy_coin_BTC for BTC' or relating itself to the generic buy_crypto_price sibling.

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 context is implied by the payment terms ('$0.25 USDC on Base', 'No account, no API key', 'Failed calls not charged'), which tell an agent this is a pay-per-call endpoint that is safe to retry on failure. There is no explicit when-to-use/when-not guidance and no reference to alternatives such as buy_crypto_price or the other buy_coin_* variants.

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