Skip to main content
Glama

SouthPow crypto & market data

buy_tok_JETT

Paid. JETT CRYPTO (JETT) 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/JETT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 behavioral burden and does a fair job: it declares the tool is paid, names the exact price and both accepted payment chains, states no account or API key is required, and specifies that failed calls are not charged. The main undisclosed behavior is freshness/latency of the quoted price and the response format, which matters for a live market-data call.

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?

Five short fragments, zero filler, and everything an agent needs is front-loaded: paid flag first, then what data is returned, then cost/rails, then failure policy. The raw endpoint URL at the end is compact and optional rather than noise.

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 tool, this covers what matters: the fields returned are enumerated inline (USD price, 24h change, market-cap rank), plus payment and billing semantics. What is missing is small but real — response encoding and how current the 'live' price actually is.

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 add; baseline 4 applies. The description correctly makes the call look parameterless by not implying any inputs, and instead spends its words on cost and transport details.

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 the exact resource and the exact payload: 'JETT CRYPTO (JETT) price: live USD price, 24h change and market-cap rank.' That is a specific verb-plus-resource statement an agent can act on. It does not, however, distinguish this from the generic sibling buy_crypto_price, which is the one ambiguity in an otherwise unambiguous purpose.

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?

Usage is implied rather than stated: you call this when you want JETT's price. The purchase preconditions ($0.01 USDC on Base or Solana, no account/API key, failed calls not charged) are genuinely useful context, but there is no explicit when-to-use/when-not guidance and no pointer to the alternative generic price tool among ~900 siblings.

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