Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OZO

Paid. Ozone Chain (OZO) 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/OZO.

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

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?

With no annotations supplied, the description carries the whole burden and does a good job: it discloses that calls are paid, the exact price ($0.05 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and even the endpoint URL. Missing are rate limits, caching/freshness guarantees, and response/error shape, which keeps it from a 5.

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 'Paid.' then purpose then cost and terms — every clause carries information and nothing is padded. The terse, fragmentary phrasing is efficient, though the jump from data fields to billing to URL is slightly telegraphic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 paid endpoint, the description covers what it returns, what it costs, on which chains, auth requirements, and failure billing. There is no meaningful gap an agent would need filled before calling it.

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 the baseline is 4 and there is no parameter semantics to explain. The description correctly implies a fixed, parameterless call scoped to a single token rather than suggesting any 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?

The description names the exact resource (Ozone Chain / OZO) and the three data points returned: live USD price, 24h change, and market-cap rank. That is far more specific than a name-only restatement. It does not explicitly contrast itself with the many sibling price tools (e.g. buy_tok_OZA or the buy_coin_* family), so token identity is the only differentiator.

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 implied by the token name and the listed fields, and the payment/preconditions are stated, but there is no explicit 'use this when…' framing and no pointer to an alternative sibling for similar price data. An agent must infer that this is the OZO-specific endpoint rather than a general crypto price tool.

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