Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ZENT

Paid. Zentry (ZENT) 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/ZENT.

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

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?

No annotations are supplied, so the description carries the full burden and does well: it discloses that the call is paid, the exact cost ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, that failed calls are not charged, and the underlying endpoint URL. Missing are rate limits, caching/freshness guarantees, and error semantics, which are the remaining meaningful behaviors for a metered endpoint.

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?

Telegraphic but every clause earns its place, and the most decision-relevant fact ('Paid.') is front-loaded. Cost, chains, auth posture, billing guarantee, and URL follow in a tight sequence with no filler.

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 parameters and no output schema, the description must name the returned fields and the access mechanics — it does both (price, 24h change, market-cap rank; $0.05 USDC on Base/Solana, no auth). It stops short of describing response shape, units, or data freshness beyond 'live', which is the small remaining 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 schema is an empty object with zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The asset and denomination are fixed by the tool itself, and the description correctly implies no caller-supplied inputs are needed.

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?

States the exact asset (Zentry, ticker ZENT) and the exact payload: live USD price, 24h change, market-cap rank. That is a specific verb+resource statement that separates it from the hundreds of sibling price endpoints by ticker. It does not flag the near-collision with buy_coin_ZEN (Horizen) or explain why buy_tok_* exists alongside buy_coin_*, so sibling differentiation is by ticker string alone.

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?

Implied usage is clear (call this to get ZENT price data), and the paid-call logistics tell an agent what invoking it costs. But there is no explicit when-to-use/when-not guidance, no mention of an alternative tool (e.g. buy_crypto_price or buy_coin_*) for broader price lookups, and no advice on whether a repeated call is warranted given the per-call fee.

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