Skip to main content
Glama

SouthPow crypto & market data

buy_tok_UQC

Paid. Uquid Coin (UQC) 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/UQC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does a decent job: it discloses commercial cost ($0.05 USDC), accepted payment chains (Base or Solana), no auth requirement, and the failure-charging policy. It omits freshness/caching and latency characteristics, and the response shape is only implied by the field list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a tight telegraphic block with the most decision-relevant fact ('Paid') front-loaded, followed by payload, price, auth, and failure policy. The raw endpoint URL at the end is of marginal value to an agent that cannot call it directly, but it costs little.

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 price lookup, the description covers everything an agent needs to decide and call: what it returns, that it costs money, how to pay, and that no credentials are needed. Only the precise response field names/formats are left unspecified, which is minor here.

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 and the description correctly introduces none, so there is no semantic gap to close. Baseline for a 0-parameter tool applies.

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 ('Uquid Coin (UQC) price') and enumerates the payload ('live USD price, 24h change and market-cap rank'), so the agent knows precisely what it gets back. It does not differentiate from the large sibling family of buy_coin_* / buy_crypto_price tools, so the agent must infer that the ticker is baked into the name rather than being told.

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?

'Paid. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged.' gives real context about cost and prerequisites, which is the main gate on calling a paid endpoint. However there is no explicit when-to-use/when-not guidance and no reference to the alternative price tools (buy_crypto_price, buy_coin_*) that could serve the same need.

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