Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ONG

Paid. Ontology Gas (ONG) 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/ONG.

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

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?

No annotations are supplied, so the description carries the full burden, and it does well: it discloses cost per call, the payment rails and currency (USDC on Base or Solana), that no auth is required, and that failed calls are not charged. It also lists the returned fields and the endpoint URL. It stops short of stating rate limits or latency/refresh cadence for a 'live' price.

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.' followed immediately by the payload description, then commercial terms, then URL — a sensible ordering for an agent deciding whether to spend. It is telegraphic (fragments rather than sentences) but every clause carries information; nothing is wasted.

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 pricing tool, the description covers what is returned, what it costs, how to pay, that auth is unnecessary, and the failure-charge policy — enough for correct invocation. Only rate limits and data freshness are unaddressed.

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; there is nothing for the description to disambiguate. The described output fields (USD price, 24h change, market-cap rank) add context but are return-value rather than parameter semantics.

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 a specific resource and verb-adjacent framing: 'Ontology Gas (ONG) price: live USD price, 24h change and market-cap rank,' which tells an agent exactly what data comes back. It does not explicitly contrast with the near-duplicate sibling buy_coin_OGN or with buy_crypto_price, so the sibling routing burden falls on 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 Guidelines3/5

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

It gives real prerequisites ('Paid. $0.01 USDC on Base or Solana. No account, no API key'), which is useful when-to-use context. But it never says when to prefer this over buy_coin_OGN or buy_crypto_price, and gives no exclusion conditions beyond payment.

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