Skip to main content
Glama

SouthPow crypto & market data

buy_coin_OCEAN

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses that the call is paid ($0.002 USDC on Base), the payment rail, that no account or API key is required, and the failure-billing policy ('Failed calls not charged'). It also names the underlying data sources (Coinbase Exchange with Kraken cross-check) and the endpoint URL, which is unusually complete disclosure for a paid data tool.

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?

Every clause is load-bearing: billing first, then what data is returned, then sources, then cost/auth/failure terms, then the URL. Fragments are used deliberately and nothing is restated from structured fields.

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?

For a parameterless, annotation-free tool with no output schema, the description supplies everything an agent needs: what is returned, at what cost, with what auth requirements, what happens on failure, and where the endpoint lives. No material gap remains.

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 and the schema is empty at 100% coverage, so there is nothing parameter-level to document; baseline is 4. The description correctly implies the asset is fixed by the tool identity rather than passed as an argument, which matches the empty schema.

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?

The description names the exact asset pair (OCEAN/USD) and enumerates the specific metrics returned: last price, 24h open/high/low, percent change, and 24h/30d volume. The ticker suffix in the name plus the quoted pair make it unambiguous which sibling to pick for OCEAN, though it never explicitly contrasts itself with generic alternatives like buy_crypto_price.

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 leading 'Paid.' and the price line signal a paid, pay-per-call tool, and 'No account, no API key' tells the agent what prerequisites are unnecessary. However, there is no explicit when-to-use/when-not guidance or pointer to a sibling (e.g., a generic crypto price tool) for cross-asset queries, leaving selection to inference.

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