Skip to main content
Glama

SouthPow crypto & market data

buy_coin_AIOZ

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

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

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 full burden and does well: it discloses that the call is paid ($0.10 USDC on Base), requires no account or API key, that failed calls are not charged, and names the upstream data sources and endpoint URL. It stops short of stating rate limits, data freshness/caching, or response encoding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with no filler: payment and price are front-loaded ('Paid.'), the returned fields follow, then cost/auth/failure policy and the URL. Every fragment earns its place and nothing is repeated.

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 parameterless, annotation-free price endpoint with no output schema, the description covers cost, payment rail, auth requirements, billing on failure, returned fields, sources, and endpoint. Only response format and freshness/latency expectations are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to add and the schema is trivially complete. Baseline 4 applies for a 0-param tool, but there is genuinely nothing in the description that maps to inputs; a 3 reflects that it contributes nothing on this dimension beyond confirming the tool is parameterless.

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: AIOZ/USD last price, 24h open/high/low, % change, 24h and 30d volume, with named sources (Coinbase Exchange, Kraken cross-check). The symbol in the name already separates it from the other buy_coin_* siblings, but the description never distinguishes it from the generic buy_crypto_price sibling, so an agent has no stated basis for choosing between them.

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 only implied by the payload contents — an agent infers it should call this when it needs AIOZ spot/24h stats. There is no explicit when-to-use statement, no exclusion, and no pointer to buy_crypto_price as the generic alternative or to any other sibling.

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