Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CRV

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

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

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, the description carries the full burden and does so well: it discloses that the call is paid, the exact price and chain ($0.01 USDC on Base), that no auth is required, that failed calls are not charged, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It omits latency/caching behavior and the payment flow mechanics, which keeps it from a 5.

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?

A single dense sentence plus a URL and short cost/auth clauses; every fragment carries information (data fields, sources, price, auth, billing, endpoint). Nothing is repeated or padded, and the payload description is front-loaded before the commercial terms.

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 compensates by enumerating the returned metrics and their upstream sources. The remaining gap is how the USDC payment is actually settled (wallet handshake, x402 flow), which an agent would need to know to invoke it successfully.

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 baseline is 4 and there is no schema surface for the description to elaborate on. The field list (last, open/high/low, % change, 24h and 30d volume) usefully describes the output rather than inputs.

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 specific resource and its scope: 'CRV/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', which is far more concrete than the opaque tool name 'buy_coin_CRV'. It does not, however, explicitly differentiate itself from the hundreds of sibling ticker tools or from buy_crypto_price, leaving sibling routing to be inferred from the ticker suffix.

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 key prerequisites ('No account, no API key', '$0.01 USDC on Base', 'Failed calls not charged'), which tells an agent the access conditions. It offers no guidance on when to prefer this over buy_crypto_price or other price sources, and no when-not-to-use 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