Skip to main content
Glama

SouthPow crypto & market data

buy_cp_stablecoins-check

Paid. Live crypto prices, stablecoins check basket (USDT, USDC, DAI, PYUSD): USD median of Coinbase and Kraken, each source shown. $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/crypto-prices/stablecoins-check.

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_cp_stablecoins-check"
  }
}

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 does well: it discloses paid access, the exact price ($0.005 USDC on Base or Solana), no account/key requirement, and that failed calls are not charged. Provenance is also explicit (median of two named exchanges, each source shown). Rate limits and latency are undisclosed, which keeps it below 5.

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?

Front-loaded with 'Paid.' so cost is the first thing seen, then the data description, then payment and auth terms. It is dense but readable; the trailing URL largely duplicates the tool name and is the only near-wasted clause.

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, no-annotation tool, the description covers what is returned (per-source and median USD prices), what it costs, how to pay, and that no credentials are needed. Only the exact response shape is left unstated, which is a minor gap given there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4, but the description adds nothing parameter-related because there is nothing to parameterize. It also doesn't state that no arguments are accepted, which an agent must confirm elsewhere.

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 concrete resource and scope: a stablecoin basket limited to USDT, USDC, DAI, and PYUSD, with the price defined as the USD median of Coinbase and Kraken. That scope statement implicitly separates it from the hundreds of single-coin buy_coin_* siblings, though it never names an alternative explicitly.

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?

The description gives purchasing context (paid, no account or API key, failed calls free) but no when-to-use guidance against alternatives such as buy_coin_USDT or buy_crypto_price. The intended use case — one call for a four-coin stablecoin snapshot — is only inferable from the basket listing.

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