Skip to main content
Glama

SouthPow crypto & market data

buy_tok_UMINT

Paid. UBS USD Money Market Investment Fund Token (UMINT) 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/UMINT.

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

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 a good job: it declares the tool is paid ($0.01 USDC), names the payment networks (Base or Solana), states no account or API key is needed, and that failed calls are not charged — a genuinely useful billing/failure policy. What it omits is response shape beyond the three fields and price freshness/latency, 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?

Front-loaded with 'Paid.' and tightly packed: what it returns, what it costs, how to pay, and the endpoint, in roughly three sentences. Nearly every clause earns its place, though the raw URL is of marginal use to an agent invoking the tool.

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 tool, the description is largely self-sufficient: it covers the returned fields, the price, the payment rails, and the failure billing policy. A little more on response format or data freshness would make it fully complete for an agent deciding whether one call is enough.

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 no schema semantics for the description to supplement; the baseline for a parameterless tool applies. The description correctly implies no inputs are needed by saying '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: UMINT (a UBS USD Money Market Investment Fund Token) price, with the returned fields enumerated (live USD price, 24h change, market-cap rank). It is clearly distinguishable from generic siblings like buy_crypto_price because the asset is hard-coded in the tool name. It stops short of saying how it relates to the other buy_coin_/buy_tok_ families, but the resource is unambiguous.

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: call this to get the UMINT price. There is no explicit when-to-use/when-not and no named alternative (e.g., buy_crypto_price for a general quote, or one of the buy_coin_* tools for the same asset on a different rail). An agent must infer the selection rule from the tool name alone.

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