Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XEC

Paid. eCash (XEC) 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/XEC.

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

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 carries the full burden and does a solid job: it discloses that the call is paid, the exact price and accepted chains, that no auth is required, and that failed calls are not charged — a genuinely useful billing-failure policy. It stops short of rate limits, latency, or data freshness guarantees.

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?

Seven compact clauses, each carrying a distinct fact (paid, payload fields, price/rails, no auth, failure refund, endpoint). The telegraphic fragment style ('Paid.') is terse but front-loads cost first, which is the most decision-relevant item. Slightly choppy rather than flowing prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by enumerating the returned fields (USD price, 24h change, market-cap rank). Combined with pricing, auth, and failure semantics, there is nothing an agent needs to call this zero-parameter endpoint that is 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 the baseline is 4; there is nothing to disambiguate. The description even pins the symbol (XEC) and the endpoint path, so the agent does not need to supply or infer any argument.

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?

Names the concrete resource and payload: 'eCash (XEC) price: live USD price, 24h change and market-cap rank.' An agent knows exactly what it gets. It does not, however, contrast itself with the generic buy_crypto_price sibling or the buy_coin_* family, so selection still needs the name suffix to do the work.

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 (paid, $0.01 USDC on Base or Solana, no account, no API key) makes the cost and prerequisite model clear, which implicitly frames when it is appropriate to call. But there is no explicit when-to-use vs. when-not statement and no pointer to an alternative for other coins or for bulk price lookups, leaving routing to sibling tools to inference.

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