Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZEN

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

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

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 provided, the description carries the full burden and does substantial work: it discloses a per-call cost ($0.002 USDC on Base), that no account or API key is needed, that failed calls are not charged, the upstream data sources (Coinbase Exchange with Kraken cross-check), and the endpoint URL. It does not explain the payment mechanics (how the USDC is charged) or any rate limits, which keeps it short of 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?

One dense paragraph with the most decision-relevant fact ('Paid.') front-loaded, followed by payload contents, price, access conditions, and endpoint. The telegraphic list style is readable, though a couple of fragments could be merged for flow.

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

Completeness5/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 parameters, the description must describe what comes back, and it enumerates the exact price and volume fields plus the source venues. Combined with cost, auth, and failure-charging disclosure, an agent has everything needed to call it correctly.

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 nothing for the description to disambiguate; baseline of 4 applies.

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 makes clear this is a ZEN/USD price feed returning last price, 24h open/high/low, percent change, and 24h/30d volume, which overrides the misleading 'buy_coin' name implying a trade. It doesn't, however, distinguish itself from the sibling buy_crypto_price, which likely covers the same ground for many coins.

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 leading 'Paid. $0.002 USDC on Base' and 'No account, no API key' give the agent the key conditions for deciding whether to call, but usage is only implied. There is no explicit statement of when to prefer this over buy_crypto_price or the other per-coin siblings, and no when-not guidance.

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