Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ZBCN

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 front-loads 'Paid', names the exact cost ($0.01 USDC) and accepted chains (Base or Solana), states no account or API key is required, and specifies that failed calls are not charged. Gaps remain around latency, data freshness and what a successful response looks like, but the commercial and safety-relevant behavior is disclosed.

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?

Telegraphic fragments, but every one earns its place: paid status, data fields, cost, payment chains, auth requirement, refund policy, endpoint URL. The cost and payment terms are front-loaded right after the 'Paid' flag, which is the right priority order.

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?

No output schema exists, yet the description enumerates the returned fields (price, 24h change, market-cap rank), which is the key missing piece an agent would otherwise lack. For a zero-parameter paid lookup, that covers nearly everything needed to call it correctly, short of response envelope details.

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 4 applies. The fixed asset and quote currency are implicit in the tool name, which is the only input the agent supplies.

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 states the specific resource (Zebec Network / ZBCN) and the exact payload returned: live USD price, 24h change and market-cap rank. It is clearly a single-asset price lookup, but it never distinguishes itself from the large buy_coin_* family or buy_crypto_price, so the agent must infer the token identity from the tool name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of alternatives such as buy_crypto_price or the buy_coin_* siblings covering the same asset. The description explains payment mechanics but leaves the selection decision entirely to the caller.

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