Skip to main content
Glama

SouthPow crypto & market data

buy_tok_JST

Paid. JUST (JST) 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/JST.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 cost, payment chains, absence of auth requirements, the failure-billing policy, and the underlying endpoint. It omits rate limits, data refresh cadence, and error modes, which would matter for an agent budgeting paid calls.

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?

Front-loads 'Paid.' so the cost signal is seen first, then what is returned, then price/payment, then the raw URL. Every clause carries a distinct fact — pricing, auth, billing-on-failure — with no repetition.

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 paid price lookup with no output schema and no annotations, the description covers the essential decision inputs: what data comes back, what it costs, how to pay, and that failures are free. Only secondary operational details (refresh frequency, rate limits, response shape) are absent.

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; the schema-coverage baseline of 4 applies. The description correctly implies no input is needed beyond invoking it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-and-resource pair — live JUST (JST) USD price — and enumerates the exact payload (price, 24h change, market-cap rank). The ticker is embedded in both the name and the description, so it is unambiguous against the hundreds of buy_tok_* / buy_coin_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear invocation context: it is a paid call ($0.05 USDC on Base or Solana), needs no account or API key, and failed calls are free — all of which inform whether and how to call it. It never names an alternative (e.g. a broader price tool) or states when NOT to use it, so it stops short of full routing guidance.

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