Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EFAON

Paid. iShares MSCI EAFE ETF (Ondo Tokenized ETF) (EFAON) 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/EFAON.

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

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?

No annotations are supplied, so the description carries the full burden, and it does disclose the traits that matter for a paid endpoint: cost ($0.05 USDC), accepted chains (Base or Solana), no account or API key required, and that failed calls are not charged. It stops short of describing response shape, latency, or whether repeated calls are billed per invocation.

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?

Three compact sentences plus a URL, with the paid nature and the resource front-loaded so an agent can decide quickly. Every element (asset, fields returned, price, payment rails, auth, failure policy, endpoint) carries information and nothing is padded.

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?

With no parameters, no annotations, and no output schema, the description covers the essential decision inputs: what data comes back, what it costs, how to pay, and that failures are free. The main residual gap is response format/pagination detail, which is minor for a single fixed-asset price lookup.

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 schema declares zero parameters, so there is nothing for the description to clarify; baseline is 4. It correctly implies no filtering inputs are needed because the token is fixed in the endpoint.

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 (iShares MSCI EAFE ETF, Ondo Tokenized, ticker EFAON) and the specific payload (live USD price, 24h change, market-cap rank). It does not explicitly differentiate from near-identical siblings such as buy_tok_IEFAON or the generic buy_crypto_price, so an agent must rely on the ticker in the tool name to route correctly.

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 asset-specific framing — use this for EFAON price data — but there is no explicit when/when-not guidance or pointer to an alternative endpoint. The payment and access notes ('$0.05 USDC on Base or Solana. No account, no API key.') give practical preconditions but no comparative routing advice.

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