Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MINA

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden, and it does unusually well: it discloses a paid model ($0.01 USDC on Base), no account or API key required, and that failed calls are not charged. It omits rate limits, whether the price is a snapshot versus a stream, and any freshness/latency guarantee, which matter for a paid market-data call.

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 cost signal ('Paid.') is front-loaded ahead of the payload description, which is the right priority for a paid tool. The style is telegraphic and each clause earns its place, though the trailing raw URL is slightly redundant with the name and could be folded in.

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 zero parameters and no output schema, the description must describe the return values itself, and it does: it enumerates the fields and names the upstream exchanges. It stops short of specifying the response's shape or format and any rate or freshness constraints, which is the only remaining gap for a paid 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, which sets the baseline at 4. The description correctly adds no parameter detail because none is needed, and the symbol is hardcoded in both the name and the endpoint URL.

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?

The description names the exact resource (MINA/USD), the specific data returned (last price, 24h open/high/low, % change, 24h and 30d volume) and the sources (Coinbase Exchange, Kraken cross-check). Because the sibling set is a symbol-per-tool family, the symbol embedded in the description is precisely what distinguishes this tool from buy_coin_BTC or buy_coin_ETH.

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 infers it should call this for MINA spot price data. There is no explicit when-to-use statement, no exclusion, and crucially no routing hint toward buy_crypto_price or the other symbol variants, which an agent must disambiguate from the name alone.

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