Skip to main content
Glama

SouthPow crypto & market data

buy_tok_U

Paid. United Stables (U) 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/U.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 behavioral burden and does reasonably well: it discloses that calls are paid, the exact cost and accepted chains, that no authentication is required, and that failed calls are not billed — the failure/billing policy is the most valuable piece here. It omits rate limits and any note on caching or response freshness.

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?

Front-loaded with what the tool returns, then cost, then access terms — every clause carries a fact an agent needs before calling. No filler or restatement of the name.

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 price endpoint with no output schema, the description covers content, price, chains, auth, and failure billing, which is nearly everything needed to decide and call. It would be complete at 5 if it hinted at the response shape or the distinction from the stablecoin and generic crypto-price siblings.

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 a fixed single-symbol endpoint rather than leaving the agent hunting for an input.

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 resource and verb: retrieves United Stables (U) price data, and enumerates exactly what comes back (live USD price, 24h change, market-cap rank). It does not name or differentiate against the obvious neighbors such as buy_stable_u or buy_crypto_price, so an agent must infer the distinction from the tool name alone.

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?

Conveys the payment and access context (paid, $0.05 USDC on Base or Solana, no account or API key, failures not charged), which tells the agent this is a one-shot paid lookup. It gives no explicit when-to-use versus buy_stable_u or buy_crypto_price, and no guidance on freshness or when to re-call.

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