Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OHM

Paid. Olympus (OHM) 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/OHM.

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

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 available, the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not billed. That failure-billing and auth disclosure is exactly the kind of context annotations would otherwise supply. The remaining gap is rate limits and response shape, which keeps it off a 5.

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 payload, then cost, then constraints, then the endpoint. Six short clauses, each carrying distinct information — no padding or repetition.

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 description covers the four things an agent needs before spending money: what it returns, how much it costs, what auth is required, and what happens on failure. Only the precise response structure and latency/rate-limit behavior are absent, a minor gap given the enumerated fields.

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 input schema is an empty object with zero parameters and 100% coverage, so there is nothing for the description to disambiguate. Baseline for a zero-param tool is 4, and nothing here misleads about inputs.

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 resource (Olympus/OHM) and enumerates what comes back: live USD price, 24h change, and market-cap rank. It is far more specific than a bare ticker stub. It stops short of a 5 because it never distinguishes itself from generic siblings such as buy_crypto_price or the buy_coin_* family, so the agent must infer the split from the tool name alone.

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?

Use is implied — call this when you need OHM spot price data — but there is no explicit when-to-use or when-not statement and no pointer to the alternative price tools in the sibling list. The practical constraints given (no account, no API key) help the agent decide it is callable, but they are not routing guidance.

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