Skip to main content
Glama

SouthPow crypto & market data

buy_coin_OPG

Paid. OPG/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/OPG.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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/metered nature, exact price and payment rail (USDC on Base), that no auth or API key is required, that failed calls are not charged, and the underlying data provenance (Coinbase Exchange with Kraken cross-check). It omits rate limits, latency, and what an error/402 response looks like, which are the remaining behavioral gaps for a paid endpoint.

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 single most important fact ('Paid.'), then the data payload, then cost/access terms, then the endpoint URL. Terse fragments rather than full sentences, but every clause carries distinct information with zero filler, which suits a per-asset price endpoint.

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?

There is no output schema, so the description must outline the return values, and it does: last price, 24h open/high/low, percent change, and 24h/30d volumes. Combined with cost, auth, and billing-on-failure details, an agent can decide and call correctly. Minor gaps remain around exact response shape (JSON field names) and any rate limits or retry guidance for a paid call.

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 and there is nothing for the description to disambiguate. The description appropriately spends its words on payload and cost instead of inventing parameter explanations. No gap exists 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 payload: 'OPG/USD live: last price, 24h open/high/low, % change, 24h and 30d volume.' An agent knows exactly what data comes back. It does not explicitly say how it relates to the many buy_coin_<TICKER> siblings (i.e., that this is the OPG-specific instance and others exist per asset), so sibling differentiation rests mostly on the tool name.

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?

Gives the decision-relevant context for using it: it is a paid call at $0.25 USDC on Base with no account or API key needed, and failed calls are free. However, it never states when to prefer this over alternatives, e.g., that buy_coin_<other ticker> should be used for assets other than OPG or that buy_crypto_price exists as a generic option. Usage is implied rather than prescribed.

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