Skip to main content
Glama

SouthPow crypto & market data

buy_coin_MEZO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does well on commercial/practical traits: paid ($0.002 USDC on Base), no account or API key required, failed calls not charged, and dual-source pricing (Coinbase Exchange with Kraken cross-check). It omits operational behavior such as latency, caching/refresh cadence, rate limits, and whether the charge is per call or per successful response.

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?

Extremely dense but front-loaded: cost/status first, then the data payload, then payment and access terms, then the URL. Telegraphic fragments ('Paid.', '$0.002 USDC on Base.') are efficient rather than wasteful, though the opening 'Paid.' is cryptic until read in context.

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 endpoint, the description supplies everything an agent needs: what is returned, where the data comes from, what it costs, how to pay, and the endpoint URL. The only shortfall is the absence of refresh cadence and error/failure semantics beyond the 'not charged' note.

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 nothing for the description to disambiguate beyond confirming that no input (no ticker, no date range) is needed. Baseline 4 applies.

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 resource precisely (MEZO/USD) and enumerates the exact data returned: last price, 24h open/high/low, % change, 24h and 30d volume. The tool name's verb ('buy_coin') is misleading for a read-only price lookup, though the description corrects it immediately; the ticker in the name distinguishes it from the ~400 sibling buy_coin_* tools.

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 can infer this is the MEZO-specific price endpoint, and the Coinbase/Kraken sourcing hints at spot price use. There is no explicit when-to-use vs buy_crypto_price or when-not guidance, and no mention of what happens if a fresher/different source is needed.

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