Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TLTON

Paid. iShares 20+ Year Treasury Bond ETF (Ondo Tokenized ETF) (TLTON) 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/TLTON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 that the call is paid, the exact price and accepted payment chains, that no auth or API key is required, and that failed calls are not charged — the last being a valuable retry-safety guarantee. It stops short of describing response format or latency, which is the remaining gap for a paid endpoint.

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-loads the paid flag, then the asset and returned fields, then price/payment mechanics and the endpoint URL. The telegraphic phrasing is efficient, though the raw URL is arguably redundant given the tool already encapsulates it and slightly dilutes the prose.

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-asset price lookup with no output schema, the description supplies everything an agent needs: what data comes back, what it costs, how to pay, and that failures are free. Nothing material is missing relative to the tool's complexity.

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 no parameters, so the baseline is 4; there is no input whose meaning could be clarified. The description correctly implies all identifying information (asset, quote currency) is fixed in the endpoint itself rather than passed by the caller.

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?

States a specific resource and result set: live USD price, 24h change and market-cap rank for the iShares 20+ Year Treasury Bond ETF tokenized as TLTON. The asset identity is fully spelled out in both expanded and ticker form, so an agent can bind it to the correct sibling buy_tok_* tool without ambiguity.

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?

Gives clear context for invoking it: this is the paid TLTON price endpoint, at $0.05 USDC on Base or Solana with no account or API key needed. It does not name an alternative (e.g. a generic price tool) or state when not to use it, so the routing logic is left implicit even though the per-asset context is obvious.

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