Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AVUSD

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

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

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 supplied, the description carries the full behavioral burden and does substantial work: it declares the tool is paid, names the price and accepted chains, states no credentials are required, and guarantees failed calls are not charged. What it omits is return shape and freshness/latency, but the commercial and safety profile an agent needs before spending money is disclosed.

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?

Very tight: cost and asset scope are front-loaded, then payment terms, then the endpoint URL. Every clause carries information, though the telegraphic fragment style and the bare 'URL https://...' line read more like listing copy than prose.

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 essentials: what data comes back, what it costs, how to pay, and that failures are free. It stops short of describing the response format or data freshness, which is the main remaining gap given there is no output schema to lean 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 tool takes zero parameters, so the baseline is 4. The description correctly implies a fixed, hard-coded asset endpoint (the ticker is baked into both the tool name and the URL), so there is nothing for the agent to supply or misinterpret.

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 names a specific asset (Avant USD / AVUSD) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. That is enough to separate it from the mass of sibling buy_tok_* endpoints, though it never explains how the buy_tok_* family differs from the buy_coin_* or buy_stable_* families, which look near-identical from the outside.

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 rather than stated: an agent infers 'call this when you need the AVUSD price.' Payment mechanics ($0.05 USDC on Base or Solana, no account or API key, failed calls not charged) are covered well, but there is no explicit guidance on when to prefer this over close siblings such as buy_stable_avusd or buy_crypto_price, and no exclusions are given.

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