Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ALGO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact price and payment chain (USDC on Base), that no auth is needed, and that failed calls are not charged. It also names the upstream data sources (Coinbase Exchange with Kraken cross-check). It stops short of stating response format, freshness/latency, or rate limits.

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?

It is dense and front-loaded, leading with 'Paid.' so the agent sees the cost implication first, then the payload, price, and access terms. Every clause carries information; the trailing raw URL is slightly awkward as a standalone fragment but is functionally useful.

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 tool, the description covers what the agent needs: what data is returned, its sources, the cost and payment method, and that no credentials are required. Only the response encoding/freshness is left unspecified, a minor gap at this complexity level.

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 to disambiguate and the baseline is 4. The description usefully confirms that no inputs or credentials are required, which is the only parameter-adjacent meaning an agent needs here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (ALGO/USD live price) and enumerates exactly what comes back: last price, 24h open/high/low, % change, and 24h/30d volume. The ticker in the name plus the explicit 'ALGO/USD' in the text make it unambiguous against the many sibling buy_coin_<TICKER> tools.

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?

It states prerequisites (no account, no API key) and the commercial terms ($0.10 USDC on Base, failed calls not charged), which is useful selection context. However, it never says when to prefer this over alternatives such as the generic buy_crypto_price, nor any exclusion or rate-limit guidance, so the when-to-use logic is only implied.

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