Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GFI

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

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

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 mostly succeeds: it discloses that the call is paid ($0.10 USDC on Base), requires no account or API key, and is not charged on failure. It also names the upstream sources (Coinbase Exchange with Kraken cross-check), which tells the agent how authoritative the numbers are. It stops short of stating data freshness/latency or the payment flow mechanics.

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?

Seven short, front-loaded fragments with no filler: cost signal first, then payload, then provenance, then payment/auth terms, then endpoint. Every clause conveys something an agent or operator would act on.

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 describe return values, and it does so explicitly by listing the six data points returned. Combined with the payment, auth, and failure-charge disclosures, an agent has enough to call correctly. Only the response shape (JSON structure, units, timestamp field) is underspecified.

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 never invents parameter semantics.

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 and payload: GFI/USD last price, 24h open/high/low, percent change, and 24h/30d volume. It is distinguishable from the ~300 sibling buy_coin_* tools because the ticker is fixed per tool. However, the tool name says 'buy_coin' while the description describes a read-only price feed, a mild mismatch the description never reconciles.

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 (fetch live GFI spot price) and the cost/access lines help an agent decide whether calling is worthwhile, but the description never states when to prefer this over buy_crypto_price or get_schema, nor any exclusion such as stale or cross-asset pricing. The agent must infer the alternative-selection rule.

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