Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AGGON

Paid. iShares Core US Aggregate Bond ETF (Ondo Tokenized ETF) (AGGON) 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/AGGON.

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

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 zero annotations the description carries the full burden, and it does much of that work: it discloses that the call is paid, the exact cost and payment chains, that no auth is needed, and that failures are not charged. It stops short of describing response shape, rate limits, or how payment is submitted (e.g. x402 header), which would round out the behavioral picture.

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?

Short, front-loaded, and every clause carries information (what it returns, what it costs, where to pay, that failures are free, the endpoint URL). The telegraphic 'Paid.' opener and bare URL sentence are slightly terse but not wasteful.

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, paid, single-asset price endpoint with no output schema and no annotations, the description covers the essentials an agent needs to call it and to price the call. The main remaining gap is what a successful response looks like and any payment/transport mechanics.

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 nothing for the description to disambiguate. It implicitly makes clear the asset is fixed by the endpoint rather than passed as an argument, which is the relevant point for a zero-arg tool.

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 instrument (iShares Core US Aggregate Bond ETF, Ondo-tokenized, ticker AGGON) and the exact payload (live USD price, 24h change, market-cap rank), so an agent knows precisely what it returns. It does not explicitly contrast itself with the many sibling buy_tok_* / buy_crypto_price tools, relying on the ticker to do the differentiation.

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?

It gives practical procurement context — paid, $0.05 USDC on Base or Solana, no account or API key, failed calls not charged — which is genuinely useful for deciding whether to call. However, it never states when to use this versus alternatives (e.g. buy_crypto_price or a query tool like buy_search), nor any when-not conditions.

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