Skip to main content
Glama

SouthPow crypto & market data

buy_coin_O

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior2/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 for a paid, billed read endpoint key behavior is missing. It does well on cost ($0.25 USDC on Base), the no-account/no-key requirement, the no-charge-on-failure policy, and upstream sources with a Kraken cross-check, but it never says whether the price is real-time or delayed, what happens on a partial-source outage, or what the billing/response shape is.

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?

Front-loads the most decision-relevant token ('Paid'), then the instrument, then the field list, then price/access terms, then the endpoint. Nothing is padded; every clause carries either cost, capability, or coverage information.

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 steps in to enumerate the returned metrics, the data sources, the payment rail, and the URL. What remains thin is operational detail: freshness/latency, response format, and failure modes beyond not being charged, which for a financially-gated data call would be worth one more clause.

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. The description correctly implies a no-argument call and instead spends its words on the returned data fields, which is the right trade-off here.

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?

States a specific resource and verb-equivalent: live O/USD price with an enumerated field set (last, 24h OHLC, % change, 24h and 30d volume). The sibling family is hundreds of per-ticker buy_coin_* tools, and the ticker 'O' in the description matches the tool suffix, so an agent can tell which coin this covers. It stops short of saying explicitly that it is the O-token variant of a large per-symbol family.

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?

Useful preconditions are given: paid, no account or API key needed, failed calls not charged. However, nothing says when to pick this over buy_crypto_price or other aggregator siblings, and it never states the call fails or is unnecessary for non-O assets. Usage is implied by the ticker rather than routed.

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