Skip to main content
Glama

buy_cp_oracles

Paid. Live crypto prices, oracles basket (LINK, PYTH, BAND, API3, TRB): USD median of Coinbase and Kraken, each source shown. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/crypto-prices/oracles.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Since there are no annotations, the description handles all behavioral transparency requirements. It discloses critical information such as the payment structure ($0.01 USDC on Base or Solana), data sources (Coinbase and Kraken), and the lack of required credentials (No account, no API key).

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?

The definition is perfectly concise. Every piece of information—billing, sources, deployment chain, and failure handling—is critical context, and it is front-loaded effectively to communicate the core service immediately.

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?

The tool definition is maximally complete for its function. Given its paid nature and specific implementation requirements, it leaves no ambiguity regarding cost, source, required setup, or potential failure modes, fulfilling the agent's need for reliable execution.

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?

Although the input schema has zero parameters, the description compensates by explaining the nature of the returned data. It specifies that the tool provides the 'USD median' while showing 'each source,' which clarifies the data processing logic beyond simple data retrieval.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The purpose is perfectly clear: fetching live crypto prices specifically for a basket of listed oracles. By mentioning the specific oracles (LINK, PYTH, BAND, API3, TRB), it immediately differentiates its function from broader price tools or the singular buy_coin siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides highly effective usage guidelines by detailing the operational constraints. It specifies that the service is 'Paid' and notes that 'failed calls not charged,' setting clear expectations for commercial and technical usage.

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