Skip to main content
Glama

SouthPow crypto & market data

buy_coin_OGN

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

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

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 price ($0.01 USDC on Base), the payment rail, that no authentication is needed, and that failed calls are not charged. It stops short of describing settlement mechanics, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, telegraphic and front-loaded: paid status first, then payload, then price, then access terms, then endpoint. Every clause carries an operational fact and there is no filler.

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 convey the return shape, and it does by enumerating the metrics and source exchanges (Coinbase Exchange with Kraken cross-check). Missing only secondary details such as the response encoding and how the $0.01 is actually paid.

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 the description needs to disambiguate; the schema is empty and the description correctly does not invent inputs. The URL hint suggests the symbol is encoded in the endpoint rather than supplied by the caller.

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 specific resource (OGN/USD) and enumerates the exact data points returned: last price, 24h open/high/low, % change, 24h and 30d volume. It does not explain why the verb is 'buy' (i.e. that the purchase is of data access rather than the coin), leaving a small mismatch between name and purpose.

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?

It gives prerequisites ('No account, no API key') and cost/failure terms, which imply the tool is safe to call ad hoc, but never states when to prefer this over buy_crypto_price or the other coin siblings. The agent must infer that this is the OGN-specific variant.

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