Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SPYON

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 a good job: it discloses the paid nature, the exact cost and accepted payment rails (USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It does not cover latency, rate limits, or response shape, so it falls short of full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads 'Paid.' before anything else, then the asset, the payload, the price, the auth terms and the failure policy in dense telegraphic clauses. No filler, and the most decision-critical fact (that it costs money) leads.

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 price lookup, the description covers purpose, payload, cost, auth and failure handling — essentially everything an agent needs before calling. Minor gaps: no indication of response format or freshness/caching behavior.

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; there is nothing for the description to clarify beyond the fixed asset baked into the endpoint. The included URL reinforces that all inputs are pre-bound, which is a small useful confirmation.

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 with full identity disambiguation: 'SPDR S&P 500 ETF (Ondo Tokenized ETF) (SPYON)', plus exactly what is returned (live USD price, 24h change, market-cap rank). An agent can distinguish this from siblings like buy_tok_SPY, buy_tok_SPYX and buy_tok_SPYB purely from the description.

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?

The description establishes the decision-relevant context (it is paid, $0.05 USDC, on Base or Solana) but never states when to choose this over alternatives such as buy_tok_SPY or a generic price tool, nor any when-not conditions. Usage is only implied by the asset identity, which is adequate for a single-asset endpoint but leaves routing to inference.

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