Skip to main content
Glama

SouthPow crypto & market data

buy_tok_UMBRA

Paid. Umbra (UMBRA) 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/UMBRA.

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

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 supplied, the description carries the full burden and does well: it discloses the paid nature, exact cost ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of explaining how payment is actually executed (auto-charged vs. pre-funded balance) and gives no latency or rate-limit context, which keeps it below a 5.

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?

Six telegraphic fragments with no filler; the value proposition and price come first and the operational facts follow. Slightly staccato phrasing ('Paid.' as a standalone lead) costs some readability, but nothing is wasted.

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-annotation, no-output-schema endpoint, the description covers what is returned, what it costs, on which chains, and the auth-free access model. The one meaningful gap is the payment mechanics — an agent cannot tell from this text whether invoking the tool triggers an automatic charge or draws from a pre-paid balance.

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 is 4; the description correctly frames it as a fixed-symbol endpoint with no filtering options, and the embedded URL reinforces that the token is baked into the path rather than passed as an argument.

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?

States a specific verb+resource: fetches the UMBRA token's live USD price, 24h change and market-cap rank, which is concrete enough for an agent to know exactly what comes back. It does not differentiate itself from the many sibling price tools (buy_coin_*, buy_crypto_price), leaving the agent to infer that the differing token symbol is the sole distinction.

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 rather than stated: 'Paid... Umbra (UMBRA) price' plus 'No account, no API key' tells the agent this is a zero-setup paid lookup, but there is no explicit when-to-use vs. when-not, and no named alternative such as buy_crypto_price for general price queries or the buy_coin_* family for other tokens.

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