Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BLZ

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 it discloses cost ($0.05 USDC on Base), payment rail, no auth requirement, and billing on failure. It omits rate limits, latency, error semantics beyond billing, and response format, which are the remaining behavioral gaps for a paid endpoint.

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 the most decision-relevant token ('Paid.') and packed with specifics in three short sentences, with the endpoint URL last. The telegraphic fragment style ('last price, 24h open/high/low...') is efficient but slightly harder to parse than full clauses.

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 annotations, the description must compensate, and it largely does by enumerating the returned fields, data sources, price, and access model. Missing are rate limits, response shape, and failure behavior beyond 'not charged', so it is strong but not fully complete.

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; baseline 4 applies. The description correctly implies the asset and quote currency are baked into the endpoint rather than configurable.

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 states a specific resource: live BLZ/USD price data (last price, 24h open/high/low, % change, 24h and 30d volume) with named sources (Coinbase Exchange, Kraken cross-check). It distinguishes itself from the hundreds of sibling buy_coin_* tools by naming the exact asset, BLZ. It stops short of a full 5 because the tool name ('buy_coin_BLZ') suggests purchasing a coin while the description is a read-only price feed, and the description never explicitly reconciles that.

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

Usage Guidelines4/5

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

The opening 'Paid.' plus pricing, no-account/no-API-key, and failed-calls-not-charged give an agent the context needed to decide whether to invoke. It does not name alternatives such as buy_crypto_price or say when another tool is preferable, so it lacks explicit exclusions.

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