Skip to main content
Glama

SouthPow crypto & market data

buy_coin_AWE

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 ($0.25 USDC on Base), that no account or API key is needed, that failed calls are not charged, and that data is sourced from Coinbase Exchange with a Kraken cross-check. That is exactly the behavioral context annotations would normally provide. It omits response format, latency, and rate limits, which keeps it from a 5.

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?

Telegraphic but well ordered: cost and payment model lead, followed by payload contents, access requirements, billing policy, and endpoint. Every sentence carries information. The raw URL is of marginal value to an agent invoking an MCP tool, which is the only real waste.

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 parameters and no output schema, the description must describe the return payload itself, and it enumerates the fields (last, 24h OHLC, % change, 24h and 30d volume). Combined with the disclosed cost, auth model, and data sources, an agent has nearly everything needed to call and interpret it. Only the concrete response shape and staleness/refresh characteristics are missing.

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 the baseline is 4. The description reinforces this by fixing the pair to AWE/USD, making clear the agent cannot specify a currency or exchange, which is the only parameter-adjacent information that matters 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 states a concrete resource and payload: 'AWE/USD live: last price, 24h open/high/low, % change, 24h and 30d volume.' That is a specific verb-less but unambiguous purpose, and it usefully corrects the misleading 'buy_coin_' name by making clear this is a price feed, not a purchase action. It never differentiates itself from the hundreds of sibling buy_coin_* tools or from buy_crypto_price, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance. The description gives cost and access conditions ('$0.25 USDC on Base', 'No account, no API key') which help an agent decide whether to spend, but it never says how this differs from buy_crypto_price or from the other per-coin siblings, leaving selection to the 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