Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ZEST

Paid. Zest Protocol (ZEST) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/ZEST.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 ($0.05 USDC), accepted payment rails (Base or Solana), that no account or API key is required, and that failed calls are not charged. Missing are rate limits, latency, and the failure/error surface, which matter for an autonomous paid call.

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?

Five short telegraphic fragments, each carrying distinct information: payment status, payload contents, price and rails, auth requirements, billing policy, and the endpoint. Front-loaded with 'Paid.' so the cost implication is seen before anything else. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param paid read tool with no output schema, an agent needs cost, rail, auth, and failure billing — all present. What is absent is any hint about response shape beyond a field list (units, rank semantics, freshness) and operational limits, which for a paid endpoint the agent must budget for is a real gap.

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 input schema has zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description correctly signals that all targeting is baked into the endpoint URL rather than passed as arguments.

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 concrete resource (Zest Protocol / ZEST) and enumerates the payload: live USD price, 24h change, market-cap rank. The name already encodes the token, but the description makes the scope explicit rather than leaving it as a bare symbol. It does not explicitly contrast with the hundreds of sibling buy_tok_* tools, but the symbol-level specificity does the differentiation work.

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?

Usage context is implied by the fixed single-token scope and cost disclosure, and 'No account, no API key' removes setup questions. There is no explicit statement of when to prefer this over buy_coin_ZEST, buy_crypto_price, or buy_tok_USDC-style alternatives, leaving the agent to infer routing from the symbol alone.

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