Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TSLAON

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 it does substantial work: it declares the call is paid at $0.05 USDC on Base or Solana, requires no account or API key, and that failed calls are not charged (retry-safe cost semantics). It also exposes the underlying endpoint. It stops short of rate limits or the exact response shape, so it is strong but not exhaustive.

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.' so cost is the first thing the agent sees, then purpose, then payment rails and failure policy, then endpoint. Every clause carries distinct information with no repetition.

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-param, no-output-schema price lookup, the description covers the returned fields (price, 24h change, market-cap rank), cost, auth requirements, failure billing and endpoint. What is missing is response encoding/schema detail, which matters somewhat because no output schema exists, but the field list is enough to call the tool correctly.

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?

There are zero input parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly implies a parameterless fixed-ticker lookup, matching the empty schema.

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?

States a specific verb-and-resource pair: live USD price, 24h change and market-cap rank for TSLAON (Tesla Ondo Tokenized Stock). The ticker in the name plus the parenthetical identifying the underlying asset makes the scope unambiguous. It does not differentiate itself from near-neighbor tickers (TSLAX, TSLAB, TSLAB) or from buy_crypto_price, but the resource itself is precisely named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance. It never says to prefer this over buy_crypto_price or the other Tesla-ticker variants, and never notes that the price is only for the tokenized Ondo instrument rather than the equity. The agent must infer selection purely 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