Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FARTCOIN

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

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

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 well: it discloses that the call is paid ($0.05 USDC on Base), requires no account or API key, is not charged on failure, and aggregates Coinbase Exchange with a Kraken cross-check. It stops short of stating rate limits, latency, or the shape/error semantics of the response.

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?

Extremely dense and front-loaded: cost marker first, then the returned fields, then payment/auth/billing terms, then the endpoint. Every clause carries information an agent needs, and there is no filler.

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, no-output-schema paid endpoint, the description covers what is returned, what it costs, what auth is needed, and the billing-on-failure policy — enough to call it confidently. The only minor gap is that '% change' is not pinned to a window (presumably 24h), which an agent must infer from the surrounding 24h fields.

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 description to disambiguate; the baseline for a parameterless tool applies. The description correctly signals that no inputs are needed by emphasizing 'No account, no API key.'

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 data set returned (last price, 24h open/high/low, % change, 24h and 30d volume) and the pair (FARTCOIN/USD), so an agent knows precisely what it gets. It does not name the verb (retrieve/purchase) explicitly, and it does not distinguish itself from the near-identical sibling buy_crypto_price, leaving that differentiation to the tool name alone.

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 ticker-specific name and the listed fields — call this for live FARTCOIN/USD pricing. However, with 300+ buy_coin_* siblings and a generic buy_crypto_price available, the description offers no rule for choosing between them and no when-not-to-use condition.

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