Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ONDO

Paid. ONDO/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.05 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/ONDO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 substantial work: it discloses that the call is paid, the exact price and payment chain ($0.05 USDC on Base), that no account or API key is needed, and that failures are not charged — the key risk facts for an agent deciding whether to invoke. It stops short of stating rate limits, response format, or latency, 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.' and then the resource, so cost and subject land immediately; every clause carries a distinct fact (fields, sources, price, auth, failure policy, URL). The telegraphic style omits a subject and verb, which reads slightly like a label dump rather than a sentence, 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?

With no parameters, no annotations, and no output schema, the description must carry the whole definition, and it covers subject, returned fields, cost, auth model, failure billing, and endpoint. The main gap is that the shape/format of the returned data is unspecified, which leaves an agent guessing about parsing despite the field list.

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 semantics to explain and the baseline of 4 applies. The description adds value by making clear no input is required at all (the coin and endpoint are baked in), so an agent will not go looking for a symbol argument.

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 (ONDO/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. It also names the underlying sources (Coinbase Exchange, Kraken cross-check), which tells an agent this is a real market feed rather than a proxy. The coin symbol in the description makes it unambiguously distinguishable from the hundreds of sibling buy_coin_* tools.

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 'Paid. ... $0.05 USDC on Base. No account, no API key. Failed calls not charged.' lines give the practical conditions for calling it, which is more than most tools offer. However, there is no explicit statement of when to prefer this over buy_crypto_price or other price-adjacent siblings, nor any exclusion guidance. Usage is implied by the coin-specific name rather than stated.

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