Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZAMA

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

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

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 it delivers meaningful behavioral detail: it is a paid call costing $0.10 USDC on Base, requires no account or API key, charges nothing on failure, and cross-checks Coinbase against Kraken. What it omits is rate limits, latency/freshness of the quote, and whether the returned figure is real-time or delayed, which matter for a price feed.

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?

The most decision-relevant fact, 'Paid', is front-loaded, followed by the returned fields, then cost, auth, and failure policy. Every clause carries information, though the density (multiple facts separated only by periods) makes it slightly scannable-poor.

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 input schema, no annotations, and no output schema, the description must tell the agent what comes back, and it does by listing the exact metrics. It falls just short of complete by not indicating response format (JSON payload shape) or data freshness, which an agent calling a live price endpoint would reasonably want.

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 and the schema is empty, so there is no parameter meaning to convey and the baseline of 4 applies. The description does not waste words inventing parameter guidance that could not exist.

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?

The description states a specific resource (ZAMA/USD live price) and enumerates exactly which fields are returned: last price, 24h open/high/low, % change, 24h and 30d volume. It also names the data sources (Coinbase Exchange with Kraken cross-check), so an agent knows precisely what it is getting and can distinguish it from the hundreds of sibling ticker tools by the ZAMA symbol.

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?

The 'Paid' framing plus the $0.10 USDC-on-Base price and 'no account, no API key' note give the agent the practical context needed to decide whether to call, and 'failed calls not charged' removes downside risk. However, it never names an alternative (e.g. the generic buy_crypto_price sibling) or states when this paid feed should be preferred over it, leaving the routing decision implicit.

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