Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AO

Paid. ao Computer (AO) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/AO.

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

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 at all, the description still discloses the important behavioral facts: the tool costs money, on which chains and in what currency, that no credentials are required, and that failures are free. Not covered: latency/data freshness, whether the price is real-time or cached, and rate limits or retry semantics for a paid call.

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?

Six short clauses, front-loaded with the price payload, then cost, then auth, then the URL. No restatement of the name and no filler; every sentence carries operational information.

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 what is returned (price, 24h change, cap rank), what it costs, what it does not require, and where it lives. The only gap is return shape and freshness, which matters somewhat more here because there is no output schema to fall back on.

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 input schema is an empty object with zero properties, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly conveys that the asset is fixed by the tool rather than passed as an argument, which is the only parameter-relevant fact 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?

Names the exact asset ('ao Computer (AO)') and enumerates the payload: live USD price, 24h change, market-cap rank, plus the endpoint URL. This lets an agent distinguish it from the hundreds of buy_coin_*/buy_tok_* siblings by asset, but it never explicitly contrasts itself with the general buy_crypto_price tool, leaving a small routing ambiguity.

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

Usage Guidelines4/5

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

Supplies concrete preconditions for use: it is paid ($0.01 USDC on Base or Solana), needs no account or API key, and failed calls are not charged. That is exactly the context an agent needs before spending. It stops short of stating when to prefer this over buy_crypto_price or the buy_cp_* category tools.

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