Skip to main content
Glama

SouthPow crypto & market data

buy_coin_TOSHI

Paid. TOSHI/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/TOSHI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the commercially important traits an agent needs before spending: cost ($0.05 USDC on Base), no auth requirements, failed calls not charged, and the upstream sources (Coinbase Exchange with Kraken cross-check). What is missing is the mechanics of the response itself (format, units, staleness/caching, latency, what a 'failed call' means), so the disclosure is partial rather than rich.

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?

Front-loaded with 'Paid.' and then the payload contents, so the most decision-relevant fact arrives first. The telegraphic fragment style ('$0.05 USDC on Base. No account, no API key.') packs a lot into little space, though the trailing raw URL sentence is more operational metadata than description and slightly clutters the read.

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?

With no output schema and no parameters, the description does the work of enumerating the fields returned, the sources, the price, and the payment/auth model. An agent can decide whether to call it and what it will cost. Only the return format/units and freshness guarantees are absent, which is a modest gap for a zero-parameter quote tool.

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 and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies; the description adds no false parameter expectations either.

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 the exact resource pair (TOSHI/USD) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume, plus the data sources. That is specific enough to separate it from the ~400 other buy_coin_<TICKER> siblings. It never uses an explicit verb and never reconciles the 'buy_coin' name with the fact that what is being bought is a data quote, not the token, which keeps it just short of a 5.

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 implied by the ticker in the name and by 'live' pricing, and the description usefully notes there is no account or API key needed. However, it never states when an agent should prefer this over the general sibling buy_crypto_price, nor any case where the quote is inappropriate (staleness, unsupported pairs). No explicit when/when-not routing.

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