Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AAPLON

Paid. Apple (Ondo Tokenized Stock) (AAPLON) 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/AAPLON.

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

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, the description carries the full burden and does substantial work: it discloses the $0.05 USDC charge, the accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It does not cover rate limits, latency, or what a failure response looks like, which keeps it out of the top band.

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?

The payment flag is front-loaded and the sentence packs purpose, cost, rails, auth, and failure policy without filler. The doubled parenthetical "(Ondo Tokenized Stock) (AAPLON)" and the trailing raw URL are slightly cluttered but each element is informative.

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 read tool, the description supplies nearly everything needed: what is returned, what it costs, on which chains, whether auth is needed, and the failure-billing rule. Only freshness/update cadence and the exact response shape remain unstated.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless single-asset lookup rather than a generic query interface.

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?

The description states a specific retrieval (live USD price, 24h change, market-cap rank) for a specific asset (AAPLON, Apple Ondo Tokenized Stock), which is exactly what distinguishes it from the hundreds of buy_tok_* siblings. An agent can select it without opening the schema because the asset identity and returned fields are both named.

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?

Leading with "Paid" gives the agent an immediate cost-based decision signal, and the price/rails tell it what commitment the call entails. It stops short of naming alternatives or exclusions (e.g. when to prefer a generic price tool or the AAPLX sibling), so the routing guidance is clear but not exhaustive.

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