Skip to main content
Glama

SouthPow crypto & market data

buy_coin_TON

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

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

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, the description does real work: it discloses that the call is paid, the exact price and settlement chain (USDC on Base), that no account or API key is needed, that failed calls are not charged, and where the data comes from. It stops short of describing the payment mechanics, latency, or response format, but this is well above the norm 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?

Effectively two dense sentences with the cost qualifier front-loaded, so the agent sees the paid nature before anything else. Slightly telegraphic and the raw URL adds little for an agent that cannot call it directly, but nothing is wasted.

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?

No output schema exists, so the description carries the return-value burden and largely meets it by enumerating the fields returned. It is complete enough to decide and call, though it never states the response encoding or what a failed/uncharged call looks like.

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?

Zero parameters, so there is nothing to disambiguate and the baseline of 4 applies; the ticker and scope are fully determined by the tool identity.

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?

Names the exact resource and enumerates the returned data points (last price, 24h OHLC, % change, 24h/30d volume), plus the upstream sources (Coinbase Exchange, Kraken cross-check). An agent can tell exactly what data this ticker-specific feed yields without opening anything else.

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 cost line ($0.01 USDC, no account, no key) and the failed-calls-free clause, which tells the agent it is safe to retry on failure. However, there is no explicit when-to-use/when-not guidance and no reference to the obvious alternatives such as buy_crypto_price or the sibling per-ticker tools.

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