Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ZCHF

Paid. Frankencoin (ZCHF) 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/ZCHF.

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

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 behavioral burden and does well: it discloses that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged — the last being important cost-safety information an agent cannot infer elsewhere. It stops short of latency, data-freshness cadence, or what a failure response looks like.

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?

Roughly five short clauses, front-loaded with the 'Paid' flag and the data payload, then payment mechanics, then the endpoint URL. The telegraphic style is efficient though slightly staccato, and the bare URL is arguably redundant with the tool name.

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 tool this covers what an agent needs: what data comes back, what it costs, on which chains, that auth is unnecessary, and the failure-billing policy. Only minor gaps remain, such as response shape and freshness guarantees.

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 no parameter meaning to add; the description appropriately spends its words on cost and output instead. Baseline 4 applies for a parameterless tool.

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 asset (Frankencoin / ZCHF) and the exact payload returned: live USD price, 24h change, and market-cap rank. An agent can tell this is a single-asset spot-price purchase rather than a market-wide feed like buy_crypto_price. It does not explicitly state what separates it from other price-shaped siblings, which keeps it short of a 5.

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?

Usage is only implied by the content ('price'), with no explicit when-to-use or when-not-to-use guidance and no named alternative. The payment and chain details help an agent decide whether it can complete the call, but nothing tells it when a different pricing tool would be more appropriate.

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