Skip to main content
Glama

SouthPow crypto & market data

buy_tok_UMXM

Paid. Manadia (UMXM) 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/UMXM.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the call is paid, the exact price, the two accepted payment chains, the absence of auth requirements, and the failure-charging policy. It stops short of payment mechanics (how the charge is settled), latency, or rate limits, 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.

Conciseness5/5

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

Six short fragments, front-loaded with the paid flag and the payload contents, then cost, then access constraints, then endpoint. No sentence is redundant and nothing buries the key information.

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 no-parameter, no-output-schema lookup, the description gives the returned fields, the price, the payment rails, and the endpoint URL, which is essentially everything an agent needs before calling. The only omission is how payment is actually transacted, which an agent might need to prepare.

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 schema is an empty object and the description correctly supplies no parameter detail, instead explaining the fixed target (UMXM) that would otherwise be a parameter.

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 (Manadia / UMXM) and enumerates what is returned: live USD price, 24h change, and market-cap rank. Because the ticker is embedded in the tool name and restated with the project name here, an agent can distinguish it from the hundreds of sibling buy_tok_* tools without opening any schema.

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: an agent infers it should call this when it wants the UMXM price. The text specifies cost ($0.05 USDC), accepted chains (Base or Solana), and that failed calls are not charged, but it never says when to prefer this over a generic alternative such as buy_crypto_price, nor any prerequisites beyond 'no account, no API key'.

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