Skip to main content
Glama

SouthPow crypto & market data

buy_tok_JUP

Paid. Jupiter (JUP) 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/JUP.

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

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 supplied, the description carries the full load and does well: it discloses the price ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying endpoint URL. The main undisclosed behavior is the response shape beyond the three named fields, and there is no note on caching or data freshness.

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?

Two short sentences: the first front-loads what the data is, the second packs cost, chains, auth model, refund policy, and endpoint. Nothing is repeated and nothing extraneous remains.

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-argument, no-output-schema price tool, the definition covers payload, price, payment rails, auth requirements, and failure billing. It falls just short of complete by not describing the response structure (field names, units, timestamp) or data latency, which the absent output schema leaves undocumented.

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 nothing for the description to disambiguate; baseline 4 applies. The description correctly makes clear the coin is fixed by the tool itself rather than passed in, which prevents an agent from trying to supply a symbol 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 concrete resource and its payload: 'Jupiter (JUP) price: live USD price, 24h change and market-cap rank.' An agent knows exactly what data comes back. It does not, however, differentiate this from the large sibling families (e.g. buy_coin_JUPITER, buy_crypto_price), so the tok-vs-coin distinction is left to the name alone.

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 context is implied by the phrase 'Jupiter (JUP) price,' but there is no explicit when-to-use statement, no mention of when to prefer buy_coin_JUPITER or buy_crypto_price, and no conditions under which this tool should be avoided. The payment details tell the agent how the call is billed, not when to select it over an alternative.

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