Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BLUECHIP

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does so well: it discloses the payment model and exact price, the settlement chain (Base/USDC), that no auth is required, that failures are not billed, and the upstream data provenance (Coinbase Exchange with Kraken cross-check) plus the literal endpoint URL. Missing only operational details such as rate limits, caching/staleness, and latency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely dense but front-loaded: 'Paid.' first, then the returned data, then cost, then auth terms, then endpoint. Every clause carries distinct information and nothing is repeated from structured fields.

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, the description must describe the return payload, and it does so field by field, along with cost, auth, and data sources. For a zero-parameter paid data tool that is nearly complete; only refresh cadence and rate/usage limits are absent.

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 is 4. The ticker and quote currency are baked into the tool rather than passed as arguments, and the description makes that fixed scope clear.

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 (BLUECHIP/USD) and enumerates precisely what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. It never uses an explicit verb like 'fetch' or 'returns', relying on the name and 'live:' framing, but an agent can still tell unambiguously what data it gets. Sibling differentiation comes from the ticker in the tool name rather than the description text.

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?

It states the call is paid, costs $0.002 USDC on Base, needs no account or API key, and that failed calls are not charged — useful cost/eligibility context for deciding whether to call. However, there is no guidance on when to prefer this ticker-specific tool over the generic sibling buy_crypto_price, nor any exclusion or fallback advice.

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