Skip to main content
Glama

SouthPow crypto & market data

buy_tok_UCN

Paid. UCHAIN (UCN) 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/UCN.

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

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 behavioral burden and does substantial work: it discloses the cost, both accepted payment rails (USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged — an important risk-reversal for a paid call. It stops short of rate limits, latency, or freshness guarantees beyond the word 'live', 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?

Front-loaded with 'Paid.', which is the single most decision-relevant fact, then payload, then price/rails, then guarantees. Every clause — cost, chain options, no-key, no-charge-on-failure — removes a distinct doubt and none is redundant.

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-argument, no-output-schema tool, the description covers cost, payment, auth, failure policy, and return fields, which is nearly everything an agent needs to call it correctly. Only rate limits and update cadence are unaddressed.

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 schema has zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The URL field usefully pins the endpoint even though no arguments are accepted.

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?

States a specific resource (UCHAIN / UCN) and enumerates exactly what comes back: live USD price, 24h change, market-cap rank. An agent can tell this apart from the hundreds of sibling buy_tok_* tools by the ticker in the name and the concrete payload description, 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?

'Paid.' plus the price line implicitly signals when a paid lookup is worth it, but no alternative is named. The description never says how this differs from buy_crypto_price or buy_coin_UCN (if it exists), leaving the agent to infer routing from the ticker suffix 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