Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SAI

Paid. Sai (SAI) 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/SAI.

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

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?

No annotations exist, so the description carries the full burden, and it does a solid job: it discloses the paid nature, the exact price and accepted payment chains, the no-auth requirement, and the important billing behavior that failed calls are not charged. It stops short of stating rate limits, data freshness/latency, or the concrete response format.

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?

Very tight and front-loaded — payment status, payload, price, auth, billing, and endpoint all land in six short fragments with no filler. The telegraphic style costs a little readability compared with full sentences, but 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?

For a zero-parameter, single-purpose paid lookup with no output schema, the description covers nearly everything an agent needs before calling: what comes back, what it costs, how to pay, and that failures are free. Only response shape and freshness guarantees are absent, which are modest gaps for this complexity.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description instead confirms the asset is fixed (SAI) rather than passed in, which is consistent with the empty input 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?

Names the specific resource (Sai / SAI) and enumerates exactly what the payload contains: live USD price, 24h change, and market-cap rank. An agent can tell this is a single-asset price lookup. It does not, however, differentiate itself from the large sibling families that appear to serve similar data (buy_crypto_price, buy_coin_*), so which one to pick remains ambiguous.

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?

Provides useful pre-call context — it is a paid endpoint, costs $0.05 USDC on Base or Solana, and requires no account or API key. What is missing is selection guidance: nothing says when to use this instead of the generic buy_crypto_price or a buy_coin_* variant for the same asset, so the alternative routing is left 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