Skip to main content
Glama

SouthPow crypto & market data

buy_coin_OPN

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the paid nature, the exact price ($0.002 USDC on Base), that no account or API key is needed, and the notably useful retry-friendly policy that failed calls are not charged. Missing only rate limits, response format, and latency expectations.

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-loaded with the single most decision-relevant token ('Paid.'), then the data contract, then cost, then auth/error policy, then endpoint URL. Telegraphic but every clause carries information an agent needs before spending money.

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 paid endpoint with no output schema, the field enumeration effectively substitutes for a return-value spec, and cost/failure/auth behavior is covered. Only the response encoding and unit conventions (e.g. volume currency) are left unstated.

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. The description instead spends its words on what the call returns, which is the relevant substitute 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 concrete resource (OPN/USD price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. The base/source pair (Coinbase Exchange with Kraken cross-check) further pins down the data, so an agent can distinguish this from the hundreds of sibling per-coin tools without opening any 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?

Implicit guidance only: it is clearly the tool to call for OPN/USD spot data, but there is no explicit statement of when to prefer it over buy_crypto_price or the generic price siblings, and no exclusions. The payment/auth notes help an agent decide it *can* call it, not *when* it should.

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