Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XAVA

Paid. Avalaunch (XAVA) 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/XAVA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 the paid nature, exact price and accepted chains (Base or Solana), that no account/API key is needed, and that failed calls are not charged, plus a direct endpoint URL. What is missing is any statement of response shape or data freshness guarantees beyond the word 'live'.

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?

It is two compact sentences that front-load the tool's purpose and then the payment terms, with no filler. The terse subject-less phrasing ('Paid. Avalaunch (XAVA) price: ...') is slightly clipped but readable and dense with relevant facts.

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 price endpoint, the description covers what is returned, what it costs, how to pay, and that failures are free — everything an agent needs to decide to call it. Only the response format and error semantics remain unstated, which is a minor gap for a tool this simple.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which sets the baseline at 4, but there is genuinely nothing parameter-related to clarify. The description confirms that no inputs (no ticker, no chain selector) are required, which is mildly useful but not a substitute for full credit.

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 the specific asset (Avalaunch/XAVA) and enumerates the returned data points: live USD price, 24h change, and market-cap rank. It is clear enough to distinguish from generic tools like buy_crypto_price, but it never explicitly contrasts itself with the many sibling buy_coin_*/buy_tok_* price tools, leaving the agent to infer which to pick.

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 by the resource name; there is no explicit 'use this when...' statement or exclusion against alternatives such as buy_crypto_price or a coin-listing tool. The payment and access notes ($0.01 USDC, no account, no API key, failed calls not charged) tell the agent about cost prerequisites but not selection criteria.

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