Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XT

Paid. XT.com (XT) 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/XT.

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

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 a solid job: it discloses that the call is paid, the exact price and accepted payment rails (USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. The main gaps are data freshness/latency and any rate or concurrency limits on the paid endpoint.

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 definition is short and front-loaded, leading with the payment flag and the resource before the logistics. Each sentence carries information (cost, rails, auth, failure policy, endpoint), though the raw URL at the end is of marginal value to an agent that already has the tool bound.

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 correctly compensates by enumerating the returned fields (USD price, 24h change, market-cap rank). Payment mechanics and the no-auth requirement are fully covered for a zero-parameter paid read tool. Only freshness expectations and error semantics beyond the no-charge-on-failure note are missing.

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 nothing for the description to disambiguate beyond confirming that no input is required. The description implicitly confirms this by stating no account or API key is needed. Baseline 4 applies for a parameterless tool.

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 (XT.com / XT) and enumerates exactly what is returned: live USD price, 24h change and market-cap rank. That is a clear verb+resource statement an agent can act on. It does not, however, differentiate itself from the large family of sibling token tools (e.g. buy_coin_XT or the generic buy_crypto_price), so the distinction must be inferred from the tool name alone.

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 can infer it should call this when it needs XT price data, and the payment terms ($0.05 USDC, no account or API key) tell it what is required to proceed. There is no explicit guidance on when to prefer this paid endpoint over a free sibling such as buy_coin_XT or buy_crypto_price, which is the most consequential routing decision here.

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