Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZRX

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

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

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?

With no annotations at all, the description carries the full load and does well: it declares the tool is paid, names the price and payment chain ($0.10 USDC on Base), states no account or API key is needed, and says failed calls are not charged. What it omits is freshness/caching behavior and whether the prices are real-time or delayed, which an agent spending money would want to know.

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?

Dense and front-loaded: the cost notice ('Paid.') leads, followed by the data fields, then terms and endpoint. Every clause carries information. The raw endpoint URL is the one piece that adds little for an agent that can't fetch URLs directly.

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?

No output schema exists, so the description must describe return values, and it does by listing the exact metrics plus the source venues (Coinbase Exchange with Kraken cross-check). Missing pieces are response shape and data latency, but for a zero-param data lookup this is close to 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 the baseline of 4 applies. The description doesn't need to explain any inputs and doesn't waste space pretending to.

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 (ZRX/USD live price) and enumerates exactly which data points come back: last price, 24h open/high/low, % change, 24h and 30d volume. That is clear enough to distinguish it from anything else. It never explicitly says 'this is a price lookup, not a trade', which matters because the tool name buy_coin_ZRX implies a purchase.

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 framing at all: no mention of when an agent should pick this over the generic buy_crypto_price sibling, no guidance on when ZRX price data is or isn't useful, and no exclusions. The only usable cue is the implicit 'this is ZRX-specific', which the agent must infer from the name.

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