Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ZYLO

Paid. Zylo Ecosystem (ZYLO) 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/ZYLO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the burden and handles it unusually well: it discloses the paid model, the $0.01 USDC price, the accepted chains (Base or Solana), and the refund policy for failed calls. It stops short of return format, latency, or payment flow mechanics, which are real gaps for a paid tool with no output schema.

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?

It is short, front-loaded with the 'Paid.' flag, and every fragment carries information — asset, payload, price, chains, auth, refund policy. The telegraphic style borders on a price list rather than prose, but nothing is redundant.

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, no-output-schema price endpoint this covers the decision-relevant facts: cost, payment rails, no authentication, failure billing, and what data comes back. Only the absence of any comparison to the many sibling price tools keeps it from being fully self-sufficient.

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?

There are zero parameters, so the baseline is 4 and nothing in the description needs to compensate. The URL and payload summary are useful context but do not function as parameter documentation.

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?

Names the specific resource (Zylo Ecosystem / ZYLO price) and the exact payload returned: live USD price, 24h change, market-cap rank. It never distinguishes itself from the very similar buy_crypto_price or buy_coin_* family, so an agent must infer the difference from the 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 Guidelines3/5

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

The single-purpose nature makes the when-to-use case implied, and the description does address prerequisites such as no account and no API key. However it gives no explicit when-not guidance and never mentions buy_crypto_price as the general alternative for price lookups.

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