Skip to main content
Glama

SouthPow crypto & market data

buy_tok_COD

Paid. CloudBank (COD) 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/COD.

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

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 supplied, the description carries the full disclosure burden and does substantial work: it flags the tool as paid, quantifies the cost at $0.01 USDC, names the accepted settlement chains (Base or Solana), states no account or API key is required, and specifies that failed calls are not charged. What is missing is any note on data latency, caching, or request limits, which are relevant for a metered live-price endpoint.

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?

Five short clauses, front-loaded with the billing flag before the payload, which is the right order for a paid call. The raw URL is arguably redundant with the tool identity, but it is defensible given the payment-per-call model and costs only a few tokens.

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-output-schema price lookup, the definition covers the data returned, the price, the payment rails, and the failure-billing policy, which is what an agent needs before spending money. Gaps are minor: no response shape, no freshness guarantee, and no statement of what happens if payment is insufficient.

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 there is nothing for the description to disambiguate and the baseline applies. The description correctly implies no inputs are needed by stating the token and endpoint inline rather than asking the caller to supply a symbol or currency.

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 payload: CloudBank (COD) USD price, 24h change and market-cap rank, so an agent knows exactly what data comes back. However, it never differentiates itself from neighbouring tools in a family of hundreds of near-identical buy_tok_* endpoints, nor from the generic buy_crypto_price, so the token-symbol match is the only disambiguator.

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 only implied: an agent that wants COD's spot price should call this. There is no explicit statement of when not to use it, no pointer to buy_crypto_price for other tokens or to the buy_coin_*/buy_tok_* families, and no guidance on freshness or repeated calls. In a 500+ sibling namespace, that omission matters.

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