Skip to main content
Glama

SouthPow crypto & market data

buy_coin_JUPITER

Paid. JUPITER/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.002 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/JUPITER.

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

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 present, the description carries the full burden and does well: it discloses that the call is paid, the exact price and payment rail, that no auth is required, that failed calls are not billed, and which exchanges back the numbers. Missing only secondary traits such as rate limits, latency, or failure/error semantics beyond billing.

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 dense, front-loaded with the payment flag before the payload and terms. Every clause carries information, though the telegraphic, punctuation-chained style reads more like a listing than prose and the raw endpoint URL is of marginal use to an agent.

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, no-output-schema price lookup, the description covers what is returned, where the data comes from, and the commercial terms, which is enough to call it correctly. It does not describe the response shape or units (e.g., how volume is denominated), a minor residual gap.

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 and the schema is empty, so there is nothing for the description to disambiguate; the baseline for a zero-param tool applies. The description correctly implies the ticker is baked into the endpoint URL rather than supplied as an argument.

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 a specific resource (JUPITER/USD live price) and enumerates exactly which data points are returned: last price, 24h open/high/low, % change, 24h and 30d volume, plus the underlying sources. That distinguishes it from the generic sibling buy_crypto_price and from other buy_coin_* tickers without opening the schema. It stops short of explicitly naming the sibling it replaces, which keeps it from a 5.

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 ($0.002 USDC on Base), the no-account/no-API-key condition, and the no-charge-on-failure policy give useful preconditions for deciding to call it. However, there is no explicit when-to-use guidance relative to buy_crypto_price, and no statement about when not to call it (e.g., if a free endpoint exists).

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