Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ITOTON

Paid. iShares Core S&P Total US Stock Market ETF (Ondo Tokenized ETF) (ITOTON) 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/ITOTON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 whole burden and does so well: it discloses the paid model, the price and accepted chains, that no auth is required, and that failed calls are not charged — a meaningful error-handling guarantee. It omits rate limits, how payment is actually settled, and response shape, 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?

Roughly three short sentences of dense, front-loaded information with no filler; the payload is stated first, then cost and access terms. Staccato fragments ('Paid.', the bare pricing clause) read slightly telegraphic, but nothing is wasted.

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 endpoint, the description covers what the agent needs to decide and call: what is returned, what it costs, on which chains, and that no credentials are needed. Missing only peripheral detail such as rate limits or how the USDC payment is authorized.

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 for the description to add; per the baseline for parameterless tools, a 4 is appropriate. The one useful detail — that the asset is fixed by the tool rather than passed in — is implicit in the naming.

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?

Names the exact asset (iShares Core S&P Total US Stock Market ETF, Ondo-tokenized, ticker ITOTON) and the exact payload returned: live USD price, 24h change, market-cap rank. Despite hundreds of near-identical buy_tok_* siblings, the full asset name plus ticker makes the target unambiguous without opening the schema.

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

Usage Guidelines4/5

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

The 'Paid.' lead, the $0.05 USDC charge on Base or Solana, and 'No account, no API key' tell the agent upfront what invoking costs and what prerequisites exist, which is genuine usage context for a paid endpoint. It does not name an alternative (e.g. a free coin-price route) or state when not to call it, so it stops short of a full routing rule.

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