Skip to main content
Glama

SouthPow crypto & market data

buy_coin_COTI

Paid. COTI/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.05 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/COTI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses that the call is paid, the exact price and payment rail, that no authentication is required, and that failed calls are not billed — the single most useful behavioral fact for an agent deciding whether to retry. It stops short of rate limits, latency, or response format, which keeps it off a 5.

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?

Telegraphic fragments, but deliberately so: billing risk is front-loaded in a single word, then the payload, then cost, then access terms, then the URL. Every clause carries information; only the trailing bare URL is arguably redundant with the endpoint metadata.

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?

Given no output schema and no annotations, the description compensates by naming the returned fields and their provenance, so an agent knows what it gets for the $0.05. It lacks freshness/update-frequency and response-shape details, a modest residual gap for a live-market-data endpoint.

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 of 4 applies. The field enumeration it does supply describes outputs rather than inputs, which is a bonus rather than a parameter gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: COTI/USD live price with an enumerated field list (last, 24h open/high/low, % change, 24h and 30d volume) plus named data sources. Since the sibling family differs only by the ticker embedded in the name, the description correctly spends its words on what the payload contains rather than re-litigating which coin.

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?

Provides operational prerequisites (paid, $0.05 USDC on Base, no account or API key, failures not charged), which tells the agent it can call this without setup. However, it never states when to use this versus buy_crypto_price or a same-asset sibling, and gives no guidance on caching or call frequency despite being a paid per-call endpoint.

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