Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ZKP

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

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

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 the price ($0.002 USDC on Base), the payment rail, that no account or API key is needed, and that failed calls are not charged. It also names the upstream data sources (Coinbase Exchange with a Kraken cross-check), which is real behavioral context. It stops short of covering latency, refresh cadence, or rate limits.

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 with the single most decision-relevant token ("Paid.") followed by the data scope, then cost, then access terms. The telegraphic style ("$0.002 USDC on Base. No account, no API key. Failed calls not charged.") is dense but every fragment carries operational weight.

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?

For a zero-parameter commodity data tool with no output schema, the description covers what is returned, what it costs, what credentials are needed, what happens on failure, and where the data comes from. The only meaningful omissions are response encoding and data freshness, which an agent would otherwise 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 nothing for the description to disambiguate. The baseline of 4 applies; the description correctly implies no arguments are needed by publishing a fixed URL.

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?

"ZKP/USD live: last price, 24h open/high/low, % change, 24h and 30d volume" names the exact resource and enumerates the returned fields, so it is clear this is a market-data read rather than a trade despite the "buy_coin_" prefix. Differentiation from siblings is implicit in the coin-specific name and data scope rather than stated.

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 description gives useful preconditions (no account, no API key required, paid) but never says when to pick this over alternatives such as buy_crypto_price or the other per-coin siblings, nor any exclusion. Usage is inferable from the tool name 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