Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ETHFI

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

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

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 a solid job: it discloses that the call is paid ($0.10 USDC on Base), requires no account or API key, and that failed calls are not charged. It also names the underlying data providers (Coinbase Exchange with Kraken cross-check). Gaps remain around rate limits and whether pricing is real-time streaming or last-trade snapshot.

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?

Extremely front-loaded — 'Paid.' signals cost before anything else, then the data payload, then payment/auth/failure terms. Every clause carries information. Minor deduction for the bare endpoint URL, which is developer documentation rather than decision-relevant context for an agent.

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 and no annotations, so the description must convey what comes back, and it does by enumerating the data points and their sources. Cost, auth model, and failure charging are all covered. It stops short of describing the response structure or freshness guarantees, which matters for a price feed.

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 of 4 applies; no useful detail is missing on the input side.

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 (ETHFI/USD) and enumerates the specific fields returned: last price, 24h open/high/low, % change, 24h and 30d volume, with named sources. That uniquely identifies the tool against the huge buy_coin_* sibling set. It loses a point because it never explicitly says 'returns price data' — the verb is missing, and the name 'buy_coin_ETHFI' could mislead an agent toward an actual purchase.

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 'use this when you need the ETHFI spot price.' There is no statement of when to prefer this over buy_crypto_price or other general price tools, nor any note about when the data is stale or unsuitable. With ~300 siblings and no routing language, it leaves selection work to the agent.

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