Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XP

Paid. Xphere (XP) 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/XP.

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

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 to lean on, the description still discloses the material behaviors the agent needs: this is a paid operation, the exact price and payment chains, that it is permissionless, and that failures are not billed. It omits how payment is actually transacted and whether responses are cached or delayed, which are the remaining unknowns.

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 telegraphic fragments, front-loaded with the billing flag, then payload, then cost, then endpoint. Every clause carries information; the staccato style is slightly rough but nothing is padded.

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?

A parameterless, output-schema-less price endpoint is fully described by naming the returned fields (USD price, 24h change, market-cap rank), the cost, the payment rails, and the URL. Only the response shape and payment flow mechanics are left unspecified, which is a modest 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.

Parameters4/5

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

There are zero parameters, so the baseline is 4. The description confirms the token is fixed by the tool name rather than passed in, which removes any ambiguity about what 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?

The description names a specific resource and verb: 'Xphere (XP) price: live USD price, 24h change and market-cap rank' via a paid purchase call. It clearly differs from the audit/TVL/yield siblings, though it does not explain how it relates to the visually near-identical buy_coin_* family that also serves prices.

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 states the prerequisites for calling (paid, $0.01 USDC on Base or Solana, no account or API key) and that failed calls are free, which tells the agent how to invoke safely. It never says when to prefer this over buy_coin_XP-style siblings or buy_crypto_price, so selection guidance is only implied.

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