Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OPAL

Paid. Opal (OPAL) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/OPAL.

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

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 $0.05 USDC cost, accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying endpoint URL. It stops short of rate limits, latency/freshness guarantees, or what a failure response looks like.

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?

Six short, front-loaded fragments: what it returns, what it costs, how to pay, auth posture, failure policy, endpoint. No filler, and the paid/non-refundable terms come before the mechanics. The URL at the end is marginally redundant with the tool binding but harmless.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (no params, no output schema), yet the description still covers the return payload fields, the payment prerequisites, the chains accepted, and billing behavior on failure. There is nothing an agent needs in order to call this correctly that is missing.

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 and the baseline applies. The description correctly implies the token is fixed by the tool identity rather than passed in, which prevents an agent from hunting for an argument.

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?

Names the specific resource (Opal / OPAL) and enumerates exactly what is returned: live USD price, 24h change and market-cap rank. The verb is implicit ('price' as a lookup), but the intent is unmistakable. It does not explain how it relates to the large buy_coin_* family, which covers many of the same assets, so the sibling differentiation is only partial.

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' prefix and the price, auth and failure-charging notes make the operating context clear, and an agent can infer this is for fetching the OPAL spot quote. However, there is no explicit statement of when to prefer it over a sibling such as a buy_coin or buy_crypto_price tool, and no exclusions or prerequisites 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