Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SOFION

Paid. SoFi Technologies (Ondo Tokenized Stock) (SOFION) 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/SOFION.

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

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 supplied, the description carries the full burden and does disclose the things that matter most for a paid call: the price ($0.01 USDC), the accepted payment networks (Base, Solana), the absence of auth requirements, and the billing policy for failures. It stops short of rate limits, what a failed payment looks like, or how the quote is sourced/refreshed.

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?

The single most important constraint ("Paid.") is front-loaded, then the payload, then cost and payment rails, then the failure-billing reassurance and URL. Every clause carries distinct information with no restatement of the tool name.

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 tool with no output schema and no annotations, the description covers the return fields (price, 24h change, market-cap rank), the cost, the payment options and the endpoint. The only gap is response shape/format detail, which is modest since the returned fields are enumerated.

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 no parameter semantics to explain and the baseline is 4. The description compensates by pinning the asset identity and giving the literal endpoint URL, so an agent knows the symbol is fixed rather than something it must pass.

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 names the exact asset (SoFi Technologies tokenized stock, ticker SOFION) and the exact payload: live USD price, 24h change and market-cap rank. The per-asset sibling family (buy_tok_*) means the ticker in the name already isolates it from the hundreds of alternatives.

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 states the operational context a caller needs before invoking (paid, $0.01 USDC on Base or Solana, no account or API key, failed calls not billed), which is real precondition guidance. However it never says when to prefer this over adjacent tools such as buy_crypto_price or buy_tok_SOFID, nor what to do if the user lacks USDC on those chains, leaving the use/no-use decision implicit.

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