Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CUSD

Paid. Cap USD (CUSD) 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/CUSD.

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

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 present, the description carries the full burden and does real work: it discloses that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is required, and critically that failed calls are not charged. What is missing is anything about the response shape, latency, or when exactly the charge is triggered. That failure-policy and payment detail is well above what most definitions offer.

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?

Five short sentences, front-loaded with 'Paid.' followed by what is returned, then cost, then access requirements, then endpoint. Every sentence carries a distinct fact and none repeat the schema. 'Paid.' alone is slightly clipped, but the payoff sentence immediately clarifies it.

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 purchase endpoint, the description covers the essentials an agent needs before spending money: what data, what cost, on which chains, and the failure-charge policy. Only the return format and charge-trigger timing are left open, which is a minor gap for this complexity level.

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 and there is nothing for the description to clarify or omit. The description correctly avoids inventing parameter-like options (e.g. no implied symbol or date arguments).

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?

Names the specific resource and its payload: 'Cap USD (CUSD) price: live USD price, 24h change and market-cap rank.' An agent knows exactly what data comes back and for which asset. It stops short of distinguishing itself from look-alike siblings such as buy_crypto_price or the buy_coin_*/buy_stable_* families, so it is clear but not sibling-differentiating.

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 by the token-specific naming; the description never says when to choose this over buy_crypto_price, buy_stable_* or the buy_coin_* variant of the same asset. There are no exclusions or preconditions given beyond the implicit 'you want CUSD price data'. An agent can infer the case but gets no routing help.

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