Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ARIAX

Paid. ARIA NETWORK (ARIAX) 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/ARIAX.

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

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 present, the description carries the burden and does so well: it discloses that the call is paid, the exact price and payment chains, that no authentication setup is needed, that failed calls are not billed, and the underlying endpoint URL. It omits rate limits, latency, and caching/freshness guarantees, which is why it falls short of a 5.

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?

The text is dense and front-loaded, opening with the billing status ('Paid.') before the resource description, then payment mechanics, then the raw URL. Every clause carries information, though the endpoint URL and repeated no-account/key points add minor bulk for a zero-argument 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?

There is no output schema, so the description must convey what comes back, and it does (USD price, 24h change, market-cap rank). Combined with the cost and payment details, an agent has enough to decide and call correctly; only freshness/latency expectations are unstated.

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 meaning for the description to add beyond the schema. Baseline of 4 applies; nothing is missing or contradictory.

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 verb-resource pair (live ARIA NETWORK price with 24h change and market-cap rank) and identifies the exact asset ticker, so an agent knows precisely what data it returns. It doesn't distinguish this from near-identical siblings such as buy_tok_ARIA or the buy_coin_* series, which is the only clarity gap.

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?

It supplies real procurement context — paid at $0.01 USDC on Base or Solana, no account or API key required, failed calls not charged — which tells the agent the cost and prerequisites of invoking it. However, it never states when to choose this tool over the many sibling token-price tools, so selection guidance remains implicit.

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