Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XPIN

Paid. XPIN Network (XPIN) 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/XPIN.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description does real work: 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. Still missing are rate limits, latency, and what a successful response looks like, but the commercial and auth behavior an agent most needs before committing spend is covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short clauses, front-loaded with 'Paid.' and then what data is returned, followed by cost, rails, auth, refund policy, and the raw URL. Every sentence carries distinct information with no repetition.

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 what is returned (price, 24h change, rank), what it costs, how payment rails work, and failure billing. The remaining ambiguity is how payment is actually transacted (automatic x402-style charge vs. prior setup) and whether chain selection is automatic, which an agent might want confirmed.

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. The description correctly implies no input is needed, since the asset (XPIN) and endpoint are baked into the tool itself.

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 resource and payload: XPIN Network USD price, 24h change, and market-cap rank. The verb is implied by the 'buy_' prefix rather than stated, and nothing explains why an agent would pick this over siblings like buy_coin_* or buy_crypto_price, which cover similar price data.

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 implied rather than prescribed: 'Paid', a concrete $0.05 USDC cost, and 'No account, no API key' tell the agent this is a frictionless pay-per-call quote endpoint. There is no explicit guidance on when to prefer it over the generic buy_crypto_price or per-coin siblings, and no exclusions are stated.

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