Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ORE

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does a good job disclosing the commercial model (paid, $0.05 USDC on Base or Solana, no auth, failed calls not charged), which is exactly the context an agent needs before spending. It stops short of describing response behavior such as freshness/latency, rate limits, or what the payload 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.

Conciseness4/5

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

The text is short and front-loaded: 'Paid.' first, then payload, then cost/access, then URL — each sentence carries a distinct piece of information. The raw URL is arguably redundant metadata but does not crowd out anything important.

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, no-output-schema price endpoint, the description covers what is returned (price, 24h change, market-cap rank), how it is paid for, what chains are accepted, and that failed calls are free. The only meaningful gap is the absence of sibling disambiguation and any statement about data freshness.

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 no parameter meaning to convey and the schema is naturally complete. The description correctly avoids inventing parameters and only supplies the fixed endpoint URL.

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 concrete resource and payload: 'ORE (ORE) price: live USD price, 24h change and market-cap rank', which is clearly a read of ORE token pricing data. It does not, however, distinguish this from other pricing-family siblings such as buy_crypto_price or the buy_coin_* variants, so an agent cannot tell from the text alone which one to pick for ORE.

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 implied by the payment and access details ($0.05 USDC on Base or Solana, no account, no API key), which tells the agent it can be called without setup, but offers no explicit when-to-use or when-not-to-use guidance versus alternative price tools in the sibling list.

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