Skip to main content
Glama

SouthPow crypto & market data

buy_coin_IO

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

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

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, the description carries the full burden and does so well: it discloses cost ($0.002 USDC on Base), payment chain, that no auth is needed, that failed calls are not billed (important for retry logic), and that prices come from Coinbase with Kraken cross-check. It stops short of describing the response payload shape or any rate limits, which would matter for a paid per-call endpoint.

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?

Front-loaded with 'Paid.' and then the data inventory, so the two facts that most affect a call decision appear first. The telegraphic fragments ('$0.002 USDC on Base.', 'No account, no API key.') are efficient rather than padded, though the trailing bare URL is a little flat in an otherwise well-ordered block.

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 paid endpoint, the description covers the decisive facts: what data comes back, what it costs, what auth is needed, and whether failures are billed. The one gap is the return format (raw string vs. structured JSON), which no schema supplies either.

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 zero-param tool applies, and the description usefully confirms no inputs are required by naming the fixed asset and endpoint.

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?

Names the exact resource (IO/USD) and enumerates the returned data points: last price, 24h open/high/low, percent change, 24h and 30d volume. The ticker-scoped sibling set (buy_coin_BTC, buy_coin_ETH, ...) means the name plus this description leaves no ambiguity about which asset this returns.

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?

Prerequisites are stated clearly (paid, no account, no API key), which tells the agent it can call this without setup. However, there is no guidance on when to prefer this over the generic buy_crypto_price sibling, and no exclusions or rate-limit conditions that would affect call placement.

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