Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XCH

Paid. Chia (XCH) 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/XCH.

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

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?

No annotations are supplied, so the description carries the full burden, and it does disclose the operationally critical traits: the call is paid ($0.01 USDC on Base or Solana), no authentication is required, failed calls are not charged, and the endpoint URL is given. The main omission is whether a successful call can still return partial or stale data, and there is no note on how the payment is authorized.

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?

It is a single dense line that front-loads the 'Paid' flag and then gives price content, cost, auth, and URL in order of decision importance. Every fragment maps to a question an agent would ask; nothing is padding.

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?

With no parameters and no output schema, the description must itself convey what comes back, and it does by naming price, 24h change, and market-cap rank. It also covers the payment and auth model. The only gap is the absence of any response-format or payment-flow detail beyond the URL.

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 input schema has zero parameters, so there is nothing to document and the baseline of 4 applies. The description correctly requires no argument information and does not waste space inventing any.

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 resource and payload: live USD price for Chia (XCH), plus 24h change and market-cap rank. That is a clear verb-implied retrieval plus named fields. It does not, however, distinguish itself from the generic buy_crypto_price sibling that presumably covers the same data, so an agent has no stated reason to pick this over that one.

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 context is implied by the tool name and the 'no account, no API key' note, which tells an agent this is callable without setup. There is no explicit when-to-use or when-not-to-use statement and no pointer to buy_crypto_price or the buy_coin_* family as alternatives, so routing must be inferred.

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