Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MANA

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

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

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 at all, the description carries the full burden and does substantial work: it discloses the payment requirement, the exact price and chain (USDC on Base), the absence of authentication, and that failed calls are not billed. It also names upstream data provenance (Coinbase Exchange with Kraken cross-check), which affects trust in the numbers. It omits the response envelope/format and whether prices are cached or real-time on each 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 text is dense and front-loaded: cost and payment model first ('Paid.'), then the payload fields, then price/auth terms, then the URL. Every clause carries information, though the telegraphic comma-list style around the data fields is slightly harder to parse than full sentences. Nothing is redundant.

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 tool this covers the essentials an agent needs: what data comes back, what it costs, on which chain, that no credentials are required, and that failures are free. The main gap is that the return format (JSON shape, timestamps, units for volume) is not described and no output schema exists to compensate.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly implies the ticker is baked into the endpoint and no filtering or date arguments are available.

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 and scope: 'MANA/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', which disambiguates from the hundreds of sibling buy_coin_<TICKER> tools by pinning MANA. It also implicitly corrects the misleading 'buy_coin' name by framing this as a paid data retrieval rather than a trade. It stops short of an explicit verb phrase like 'returns' or 'fetches', but the intent is unmistakable.

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?

The description supplies important usage context — it is paid ($0.02 USDC on Base), needs no account or API key, and failed calls are not charged, which tells an agent the cost/risk model before invoking. However it never states when to use this versus the generic buy_coin_price endpoint or any alternative data source, nor any when-not-to-use condition. Usage is implied by the ticker specificity rather than stated.

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