Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CFG

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

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

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 load and does well: it discloses the price ($0.05 USDC on Base), that no account or API key is needed, that failed calls are not charged, and that data comes from Coinbase Exchange with a Kraken cross-check. It stops short of stating rate limits, latency, or caching behavior.

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?

Front-loads the critical fact ('Paid.') before anything else, then packs fields, sources, price, auth, and failure policy into one tight passage. Every clause carries information an agent needs before calling; nothing is padded.

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?

With no output schema or annotations, the description substitutes well by enumerating the returned fields and the sourcing methodology, plus payment and failure terms. It lacks only the response encoding and a statement of data freshness/latency, which would matter for a paid live-price call.

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 and the baseline applies. The description correctly implies the symbol and quote currency are fixed, avoiding any false suggestion that inputs are accepted.

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?

States the specific resource and scope: CFG/USD live price with a named field list (last, 24h open/high/low, % change, 24h and 30d volume). An agent can tell it is the CFG price feed and not a trading action despite the 'buy_coin_' prefix. It does not explicitly route to sibling feeds, but the symbol-scoped name does that job.

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: it is the tool for CFG/USD pricing data. There is no explicit statement of when to prefer this over buy_crypto_price or other coin feeds, and no note on when a cross-check source should be trusted over the primary.

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