Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AIX

Paid. AI XOVIA (AIX) 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/AIX.

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

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 that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and it names the endpoint URL. What it does not cover is how payment is presented or settled at call time, which matters for a paid tool an agent must actually execute.

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 flag and the payload description, then pricing and access terms. The telegraphic style ('Paid.', 'No account, no API key.') is efficient, though the bare URL could be labelled more clearly as the endpoint.

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-annotation, no-output-schema tool, the description covers the essentials: what is returned, what it costs, on which chains payment is accepted, and that failures are free. The one real gap is the mechanics of paying, which is the main behavioral risk for an agent invoking a paid endpoint.

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 and there is nothing the description could add on parameter meaning. The description correctly implies the ticker is fixed rather than passed in, which prevents an agent from looking for a symbol 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?

States a specific verb and resource: fetch live USD price, 24h change, and market-cap rank for the AIX token. An agent can tell this is the AI XOVIA price feed, distinct from the many buy_tok_* siblings only by the ticker, without needing a schema. It stops short of naming an alternative such as buy_crypto_price, so a 5 is not warranted.

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 only implied: an agent infers it should call this when it needs AIX pricing. There is no explicit statement of when to prefer it over buy_crypto_price or buy_coin_-style tools, and no exclusions. The access notes (no account, no API key) are operationally useful but are not selection guidance.

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