Skip to main content
Glama

SouthPow crypto & market data

buy_coin_AERO

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

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

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 behavioral burden and does reasonably well: it declares the call is paid ($0.002 USDC on Base), specifies the payment chain/currency, states no auth is required, and says failed calls are not charged — the key economic risk is covered. It does not mention rate limits, caching/delay of the quotes, or how payment is settled per request.

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?

Telegram-style but front-loaded: cost disclaimer first, then the data payload, then the access mechanics. Every clause carries information, though the trailing raw URL duplicates what the tool binding already provides and the fragmented phrasing ('Paid.') costs a little readability.

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 no-parameter tool with no output schema, the description tells the agent what fields come back, which sources back them (Coinbase Exchange with Kraken cross-check), and what the call costs. Remaining gaps are response encoding/shape and data freshness, which are secondary for a single-value market-data fetch.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The asset and quote currency are baked in and stated explicitly, so the description fully matches the empty input schema.

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?

States a specific resource and payload: 'AERO/USD live: last price, 24h open/high/low, % change, 24h and 30d volume'. This is important because the tool name 'buy_coin_AERO' could be misread as a trade execution; the description correctly reframes it as a price-data purchase. It does not, however, distinguish this from generic siblings like buy_crypto_price, relying on the ticker in the name to disambiguate.

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 by the asset-specific payload, and the practical preconditions are stated (no account, no API key, failed calls not charged). There is no explicit guidance on when to pick this over buy_crypto_price or why a per-ticker endpoint exists, so an agent in a large sibling set gets no routing help beyond the ticker.

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