Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OZA

Paid. Ozapay (OZA) 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/OZA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it declares the paid nature, the exact price ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. The endpoint URL is also exposed, which is unusually complete for a metered tool.

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 front-loaded: cost flag, payload, price, auth/billing terms, endpoint, with zero filler sentences. Every clause contributes a fact an agent could act on.

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 output schema and no annotations, the description must convey payoff, cost, auth, and result shape, and it covers all four at a high level. The only residual gap is the concrete response format (JSON fields, units, freshness/timestamp), which an agent may still want before paying.

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; the baseline applies rather than any specific parameter explanation. The description instead spends its words on cost and output fields, which is the right allocation here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and payload: 'Ozapay (OZA) price: live USD price, 24h change and market-cap rank.' Naming both the project (Ozapay) and ticker (OZA) lets an agent distinguish it from near-identical siblings such as buy_tok_OZO without opening either schema.

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 token name and payload listing; there is no explicit statement of when to call this versus e.g. buy_coin_OZA or buy_tok_OZO, and no exclusions. The payment details hint that this is a one-shot paid lookup, but no alternative or prerequisite is named.

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