Skip to main content
Glama

SouthPow crypto & market data

buy_tok_UAI

Paid. UnifAI Network (UAI) 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/UAI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 burden and does so well: it discloses the cost, the two accepted payment rails, the absence of auth requirements, and the failure policy ('Failed calls not charged'). What is missing is rate-limit, latency, or settlement behavior (e.g., whether payment is per-invocation or batched), so it falls short of fully transparent.

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?

A single dense sentence-cluster, front-loaded with the 'Paid.' flag before the purpose, then cost, then auth. Every clause carries distinct information (what, price, rails, failure policy, endpoint), with no filler.

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?

There is no output schema, no annotations, and no parameters, so the description must supply everything an agent needs. It states the subject, the exact fields returned, the price paid, how to pay, that no credentials exist, and that failures are free — sufficient to call the endpoint confidently.

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 implies no caller-side configuration is needed by stating 'No account, no API key'.

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 specific verb+resource: 'UnifAI Network (UAI) price', and enumerates the returned fields (live USD price, 24h change, market-cap rank). It is unambiguous which token this covers, which matters among the many buy_tok_* siblings, but it never explicitly contrasts itself with buy_crypto_price or buy_coin_* so an agent must infer the routing.

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 implied by the token name plus the payment terms ('$0.01 USDC on Base or Solana', 'No account, no API key'), so an agent can tell this is a pay-per-call alternative to a free price lookup. However, there is no explicit when-to-use / when-not-to-use statement or named alternative, leaving the choice between this and the free price tools to inference.

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