Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OMI

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 that the call is paid, the exact price and accepted chains (Base or Solana USDC), that no account or API key is required, and that failed calls are not charged. It omits rate limits, latency, and error semantics beyond the refund note.

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?

Front-loaded with the operative word 'Paid', then the payload, cost, auth posture, failure policy, and endpoint. Every clause carries information, though the telegraphic fragments and raw URL read more like a listing than prose.

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, single-asset price purchase with no output schema, the description covers what is returned (price, 24h change, rank), what it costs, how to pay, and that failures are free. Enough to call correctly; only rate limits and response format are unstated.

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. The description correctly implies no input is needed and identifies the asset by name in the tool itself rather than through a parameter.

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 states a specific resource and scope: live ECOMI (OMI) USD price, 24h change, and market-cap rank. It reads as a purchase of that data point. It does not name or contrast with near-identical siblings such as buy_crypto_price or the buy_coin_* family, so the agent must infer OMI-specific routing from the tool name itself.

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?

Usage is only implied: pay $0.01 USDC to get OMI price data. There is no explicit statement of when to prefer this over buy_crypto_price or another token-price sibling, and no mention of when not to call it (e.g., if the caller wants a different asset).

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