Skip to main content
Glama

SouthPow crypto & market data

buy_tok_UB

Paid. Unibase (UB) 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/UB.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden and does a lot: it declares the tool is paid, states the exact price ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is required, that failed calls are not charged, and gives the literal endpoint URL. Only rate limits, latency, and data freshness/refresh cadence are left unstated.

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?

Six short fragments, front-loaded with the payment gate ('Paid.') before the payload and cost. Every sentence carries distinct information — cost, chains, auth, failure billing, URL — with no repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 paid quote endpoint, the description supplies everything needed to decide and call: what data comes back, what it costs, how to pay, and the URL. Nothing material is missing at this complexity level.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. It correctly does not waste words on arguments and instead spends them on output content and payment mechanics.

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 (Unibase / UB) and enumerates the payload: live USD price, 24h change, market-cap rank. Within a sibling set of hundreds of near-identical `buy_tok_*` tools, this token-level specificity is exactly what an agent needs to pick the right one.

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 only implied — the agent can infer it retrieves a UB spot quote rather than, say, TVL or yield data. There is no explicit when-to-use clause and no pointer to an alternative (e.g. `buy_crypto_price` or a broader market endpoint) or to when this single-token call is preferable.

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