Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AIXBT

Paid. aixbt (AIXBT) 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/AIXBT.

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

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 this is a paid call, the exact cost ($0.01 USDC), accepted payment chains (Base or Solana), no-auth access, and that failed calls are not charged — the key risk for an agent spending funds. It omits data freshness/update cadence and failure 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?

Compact and front-loaded: what it returns first, then cost, then access terms. Every clause carries information, though the raw endpoint URL at the end is of marginal use to an agent invoking the tool.

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, fixed-payload paid endpoint with no output schema, the description covers purpose, price, payment rails and billing caveat. Only minor gaps remain (quote refresh cadence, what a failed response looks like), which are not blocking.

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 baseline is 4. The description correctly signals a fixed, argument-free invocation, meaning there is nothing for the agent to supply.

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: live USD price, 24h change and market-cap rank for aixbt (AIXBT). An agent knows exactly what data comes back. It does not explain how this differs from the large buy_coin_* / buy_tok_* sibling families, so it stops short of full sibling differentiation.

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?

Use is implied by the data listed (call when you need an AIXBT quote), and payment prerequisites are stated ('No account, no API key'). There is no explicit when-not guidance and no named alternative among the many sibling price endpoints, so an agent must infer the choice.

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