Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZRO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 well: it discloses that the call is paid, the exact price and payment rail, that no auth is required, and that failed calls are not charged — exactly the risk information an agent needs before spending money. It stops short of disclosing data freshness/latency, rate limits, or the response envelope, 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.

Conciseness4/5

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

Front-loaded and dense — payment and data scope come first, then pricing, then the URL — with no filler sentences. The telegraphic style ('Paid.', '% change') is slightly terse but costs no comprehension, and every clause carries distinct information.

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?

There is no output schema, so the description must carry the return values, and it does by enumerating every field plus the upstream sources (Coinbase Exchange with Kraken cross-check). A zero-parameter tool needs little else; only the response format and refresh cadence are left implicit.

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 no parameter semantics to explain and the baseline is 4. The description correctly implies no arguments are needed by giving the ticker, quote currency and endpoint directly in the text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: 'ZRO/USD live' with an explicit enumeration of the returned fields (last price, 24h open/high/low, % change, 24h and 30d volume). The ticker in the name plus this enumeration lets an agent confirm this is the single-coin spot snapshot for ZRO rather than the generic buy_crypto_price sibling.

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?

Gives strong operational context for calling it ($0.05 USDC on Base, no account, no API key, no charge on failure), which implicitly answers 'can I just call this?'. But it never names an alternative or exclusion — with a generic buy_crypto_price sibling and hundreds of per-ticker siblings present, the description should say when to prefer this over that, and it does not.

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