Skip to main content
Glama

SouthPow crypto & market data

buy_tok_IVVON

Paid. iShares Core S&P 500 ETF (Ondo Tokenized ETF) (IVVON) 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/IVVON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses cost ($0.05 USDC), accepted payment rails (Base or Solana), the absence of account/API-key requirements, and the refund policy for failed calls. It omits rate limits and call-failure modes beyond billing, which keeps it short of 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?

Front-loaded with the paid flag and the asset/payload, followed by cost and access conditions. Every sentence contributes; the raw endpoint URL is slightly redundant but plausibly useful for debugging.

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 price lookup with no output schema, the essential call-time facts are present: what data comes back, what it costs, which chains accept payment, and that failures are not billed. The main residual gap is the response shape and data freshness, which are not described.

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 the baseline is 4. The description correctly implies the asset is fixed by the tool itself (IVVON) rather than passed as an argument, so no parameter meaning is missing.

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 the exact asset (iShares Core S&P 500 ETF, Ondo Tokenized, ticker IVVON) and the payload returned: live USD price, 24h change, market-cap rank. Against hundreds of identically shaped buy_tok_* siblings, the ticker-specific naming plus payload description makes selection unambiguous, though the verb is implied ('price') rather than stated as 'returns/fetches'.

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 token-specific naming and the payment terms, but there is no explicit guidance on when to call this versus buy_crypto_price, buy_coin_* or the other tokenized-ETF siblings such as buy_tok_SPYON. No when-not guidance or suggested alternatives are given.

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