Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ULTIMA

Paid. Ultima (ULTIMA) 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/ULTIMA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 that the call is paid, the price and accepted chains, the no-auth requirement, and the failure-billing policy. It stops short of coverage details like rate limits, response format, or staleness/latency of the 'live' price.

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', then the data returned, then cost, auth, billing policy, and endpoint. Every clause contributes a fact an agent would act on; no filler.

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 parameterless paid price lookup with no output schema, the description covers the commercial and operational essentials an agent needs to decide and call. The only gap is the exact response shape, which isn't strictly required but would help downstream use of the values.

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 the baseline applies and there is nothing the description could add. The schema being empty also means no parameter ambiguity is possible.

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?

The description names the exact resource (Ultima / ULTIMA) and the exact payload returned: live USD price, 24h change, and market-cap rank. Given the enormous sibling list of per-asset buy_* tools, this states unambiguously which asset and which metrics this call serves.

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?

It states the payment precondition ($0.05 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged, which tells the agent how the call works. It does not say when to prefer this over a sibling, nor any exclusion such as 'use buy_crypto_price for multi-asset quotes'.

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