Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USDAI

Paid. USDai (USDAI) 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/USDAI.

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

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 a good job: it discloses that the call is paid, the exact price and accepted payment chains (Base or Solana), that no auth is required, and that failed calls are not charged — the key risk fact for a paid endpoint. It stops short of stating rate limits, payment timing, or response format.

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?

Four short sentences, front-loaded with the paid/price framing and ending with the endpoint URL. Slightly telegraphic ('Paid.' as a standalone fragment) but nothing is redundant and nothing essential is buried.

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-param, no-output-schema tool, the description covers what is returned (price, 24h change, market-cap rank), what it costs, how to pay, and the failure-charging policy. Only secondary details such as freshness/latency and response encoding are absent.

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 there is no parameter semantics to explain and the baseline is 4. The description correctly avoids inventing inputs and instead spends its words on cost and return content.

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 resource and payload: 'USDai (USDAI) price: live USD price, 24h change and market-cap rank,' so an agent knows exactly what it returns. It does not distinguish this from the many near-identical siblings (buy_coin_USDAI, buy_stable_usdai, buy_tok_*), which is the main gap at this scale of tool surface.

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?

Opening with 'Paid' plus the $0.01 price and 'no account, no API key' gives the agent enough to judge cost and prerequisites before calling. However, there is no explicit when-to-use or when-not-to-use guidance and no pointer to the competing USDAI tools, so selection among siblings is left to inference.

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