Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CHEX

Paid. Chintai (CHEX) 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/CHEX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 well: it discloses that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. The main omission is that it does not describe response shape or freshness/latency, but the commercial and access-behavior profile is unusually well covered for an unannotated tool.

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 a compact, front-loaded series of short sentences that each convey a distinct fact (paid, what is returned, price and chains, auth requirements, billing on failure, URL). Minor waste in spelling out the full URL when the tool name already implies it, but nothing meaningfully bloated.

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 paid endpoint with no output schema, the description supplies the essentials an agent needs to call it: what data comes back, what it costs and on which chains, that authentication is unnecessary, and that failures are free. The lack of any indication of response format or data freshness keeps it short of a 5.

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, which is the baseline 4 for this dimension. The description correctly implies a fixed-asset endpoint (the token is baked into the tool/URL) and introduces no parameter semantics that would need further explanation.

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 gives a specific verb and resource: a live USD price for Chintai (CHEX), with 24h change and market-cap rank named as returned fields. It does not, however, distinguish this tool from its near-identical sibling buy_coin_CHEX, which appears to expose the same underlying asset data, so an agent has no stated basis for choosing between the two families.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. The description never says why an agent should call this endpoint rather than buy_coin_CHEX or buy_crypto_price, nor does it state any conditions under which a call would be inappropriate. The only contextual hints are access terms (no account, no API key), which are not selection guidance.

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