Skip to main content
Glama

SouthPow crypto & market data

buy_coin_EDGE

Paid. EDGE/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.01 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/EDGE.

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

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?

No annotations exist, so the description carries the full burden, and it discloses several non-obvious traits: the call is paid, the exact price and payment chain (USDC on Base), no authentication required, and failed calls are not charged. That is meaningful context an agent cannot get from structured fields. It omits rate limits, latency, and the payment mechanism (e.g., x402 handshake), which are the main remaining behavioral gaps.

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?

The description is dense and front-loaded, leading with 'Paid' so cost is the first thing the agent sees, then data fields, then payment terms. The telegraphic style is efficient, though a couple of fragments (e.g., the bare URL at the end) could be slightly better integrated.

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 and no annotations, the description does the work of enumerating the returned fields and their sources, which is exactly what is needed. It is nearly complete for a zero-parameter data-fetch tool; only the response envelope shape and payment flow remain unspecified.

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 does not waste words restating parameter details, which is correct here.

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 scope: EDGE/USD live data with last price, 24h OHLC, % change, and 24h/30d volume, and it identifies the upstream sources. This clearly separates it from the hundreds of buy_coin_<TICKER> siblings by asset. It does not distinguish itself from the generic buy_crypto_price sibling, which is the only remaining ambiguity.

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?

The description states access conditions (no account, no API key) and the cost ($0.01 USDC on Base), which implies when the tool is callable. It gives no explicit when-to-use or when-not-to-use guidance relative to buy_crypto_price or other price tools, so the agent must infer selection from the ticker name alone.

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