Skip to main content
Glama

SouthPow crypto & market data

buy_tok_UMIA

Paid. Umia (UMIA) 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/UMIA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 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, and that failed calls are not charged — an important failure-policy detail. It stops short of describing rate limits, latency, or the response format, which keeps it from 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?

It is telegraphic and front-loaded: 'Paid.' first, then the data returned, then cost, then payment mechanics, then the endpoint. Every fragment carries information, though the trailing bare URL adds little for an agent that cannot fetch it directly.

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 paid lookup with no output schema, the key facts an agent needs before spending money — cost, chains, no auth requirement, no charge on failure — are all present, plus a summary of the returned fields. Only the precise response shape and freshness/timestamp semantics are left unstated.

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 and the baseline is 4. The description correctly implies no input is needed beyond the call itself, consistent with the empty schema.

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 (Umia / UMIA) and specifies the payload returned: live USD price, 24h change, and market-cap rank. It is clear this is a single-asset price lookup, though it never contrasts itself with adjacent siblings such as the numerous buy_coin_* price tools or buy_crypto_price, so an agent must infer the distinction from the naming convention alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The agent learns only that the call is paid and cheap, not why it should pick this tool over buy_coin_UMIA-equivalent or generic price endpoints in the catalog.

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