Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SLVON

Paid. iShares Silver Trust (Ondo Tokenized Stock) (SLVON) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/SLVON.

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

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 no annotations, the description carries the behavioral burden and does so well for a paid endpoint: it declares the tool is paid, the exact price and accepted chains/payment asset, that no credentials are needed, and that failed calls are not charged. Remaining gaps are rate limits and the response shape, the latter partly mitigated by listing the returned fields.

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 'Paid.' lead word plus asset identification, returned fields, payment terms, and endpoint URL are all front-loaded and each clause carries information. The telegraphic, comma-spliced style is dense but not padded; no sentence 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?

Given zero parameters, no annotations, and no output schema, the description supplies the asset identity, the returned fields, the payment/access model, and the URL, which is close to everything an agent needs to invoke it correctly. Only rate limits and any caching or freshness guarantees are left unspecified.

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 nothing for the description to clarify beyond confirming that a bare call is sufficient, which it implicitly does by giving a fixed URL per ticker. Baseline 4 applies for a parameterless 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 resource (iShares Silver Trust, ticker SLVON) and the three data points returned: live USD price, 24h change, and market-cap rank. That is enough for an agent to know this is the SLVON-specific price call rather than a generic crypto price tool, though it never explicitly disambiguates against the hundreds of sibling buy_tok_* endpoints.

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?

Cost and access conditions are stated ($0.01 USDC on Base or Solana, no account, no API key), which functions as practical guidance for calling it. However, there is no explicit when-to-use versus alternatives such as buy_crypto_price or a different token's buy_tok_* endpoint; the agent must infer the routing rule from the ticker in the name.

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