Skip to main content
Glama

SouthPow crypto & market data

buy_tok_IEFAON

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

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

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?

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses that the call is paid, the exact price and payment rails (USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. Those are genuinely useful operational facts an agent cannot get from the empty schema. It stops short of freshness/latency guarantees, rate limits, or what a failure looks like, which keeps it below a 5.

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 description is short and front-loaded: 'Paid.' leads, then purpose, then cost, then logistics, then the endpoint URL. Each sentence carries information, though 'price: live USD price' is mildly redundant and the raw URL at the end is more operational than semantic.

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, single-datum lookup with no output schema, the definition covers everything an agent needs: what is returned (price, 24h change, market-cap rank), what it costs, how to pay, that no credentials are needed, that failures are free, and where the endpoint lives. Nothing material is missing.

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 and the baseline of 4 applies. The description does not add noise by describing nonexistent inputs.

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 specific resource (iShares Core MSCI EAFE ETF, Ondo-tokenized, ticker IEFAON) and the exact data returned: live USD price, 24h change, and market-cap rank. That is a clear verb-plus-resource statement an agent can act on. It does not, however, contrast itself with the many sibling price tools such as buy_crypto_price or the other buy_tok_* entries, so differentiation rests on the name alone.

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 rather than stated: an agent can infer this is the tool to call for IEFAON pricing, and the '$0.05 USDC on Base or Solana' and 'Failed calls not charged' lines give useful cost context for deciding whether to spend. But there is no explicit when-to-use/when-not guidance and no mention of an alternative tool (e.g., a generic crypto price endpoint) for comparison.

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