Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ORDI

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/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 substantial work: it discloses the tool is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. It omits freshest-data latency/refresh behavior, but the cost and auth profile — the riskiest unknowns for a paid tool — are covered.

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, front-loaded with the 'Paid' flag before the payload description, then cost, then access terms, then the URL. Nothing is padding; the only minor redundancy is repeating ORDI inside parentheses.

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 zero-parameter, no-output-schema paid lookup, the description supplies the returned fields, the price, the payment chains, the auth requirement, the failure-billing policy and the endpoint. An agent has everything needed to decide and to call it correctly.

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; the baseline of 4 applies. It correctly makes clear the token is fixed by the endpoint rather than passed in.

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 a specific resource (ORDI token) and enumerates exactly what comes back: live USD price, 24h change and market-cap rank, with a concrete endpoint URL. It does not, however, distinguish itself from the adjacent buy_coin_* / buy_crypto_price lookups, so an agent has no stated reason to pick this over a sibling for a plain price query.

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 context is implied — a live single-token price lookup — and the payment preconditions are spelled out. There is no explicit when-to-use/when-not statement and no mention of the sibling price tools (buy_crypto_price, buy_coin_*), leaving the selection decision 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