Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AID

Paid. GAIB AID (AID) 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/AID.

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

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 does real work: it flags the tool as paid, names the exact price and payment rails (USDC on Base or Solana), states no auth is required, and promises failed calls aren't charged — all non-obvious behaviors an agent must weigh before invoking. It stops short of describing response format, latency, or whether the quoted price is real-time versus cached.

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?

Front-loads the critical 'Paid.' signal and the price/return payload before the logistics, with no filler. The telegraphic fragment style ('GAIB AID (AID) price:') is terse to the point of being slightly cryptic, but nothing is wasted.

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 purchase tool, the description covers the essentials an agent needs to decide and act: what data comes back, what it costs, how to pay, and that failures are free. It lacks only secondary details like response shape and rate limits, which is acceptable given there's 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 neither needs nor offers parameter semantics, and the token identity is baked into the tool name rather than an argument.

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 specific resource (GAIB AID token price) and enumerates the payload (live USD price, 24h change, market-cap rank), which is exactly what distinguishes it from the hundreds of sibling buy_tok_* entries. It doesn't explicitly say 'for other tokens use their corresponding buy_tok_* tool', but the token-specific naming makes the boundary clear.

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?

Provides useful purchase context — cost, accepted chains, and that no account or API key is needed — which implies 'use this when you want this token's price and can pay $0.05'. However, it never states when NOT to use it or routes to alternatives (e.g. free equivalents or bulk price tools such as buy_crypto_price), leaving the selection decision to the token 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