Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MAGIC

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well: it discloses the $0.10 USDC on Base price, that no account or API key is required, that failed calls are not charged, and which upstream venues supply the data. It omits how payment is actually settled (protocol/flow), latency, and rate limits, which are meaningful gaps for a paid endpoint but not fatal.

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 description is dense and front-loaded: payment status first, then exactly what data is returned, then cost/access terms, then the endpoint URL. The telegraphic fragment style is efficient but slightly cryptic ('Paid.' standing alone), and no sentence 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?

With no input parameters, no annotations, and no output schema, the description must cover both what comes back and what the call costs, and it does: it enumerates the returned fields and the data sources plus payment and failure-charging terms. Only the response format (JSON shape) and payment mechanics are left unspecified.

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 the schema baseline is 4 and there is nothing for the description to clarify. It correctly avoids inventing parameter talk and instead spends its words on scope and payment. No gap exists in this dimension.

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 a specific resource and scope: MAGIC/USD live price with last price, 24h open/high/low, % change, 24h and 30d volume, sourced from Coinbase Exchange with a Kraken cross-check. It is clear this is a market-data endpoint rather than an actual trade, which resolves the ambiguity of the 'buy_coin_' name. It does not explicitly say how it differs from generic siblings like buy_crypto_price, but the ticker specificity does the differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as buy_crypto_price or other buy_coin_* tickers. The only situational information is 'Paid' and 'No account, no API key', which describes prerequisites rather than tool selection. With hundreds of near-identical siblings, a routing sentence would have real value.

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