Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USX

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

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

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 behavioral burden and does so well: it discloses that the call is paid, the exact cost ($0.05 USDC), the accepted rails (Base or Solana), that no account or API key is required, and that failed calls are not charged. That last detail is a genuinely valuable billing guarantee an agent could not infer. Remaining gaps are rate limits and latency, which are minor for a single-value price lookup.

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?

The definition is short and front-loaded, leading with 'Paid.' so the cost consequence is the first thing an agent sees, followed by the data returned and then the payment mechanics. It is telegraphic in places ('USX (USX)', terse noun phrases) but no sentence is wasted.

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, an agent needs to know what comes back, what it costs, and how to pay; the description covers all three plus the endpoint URL. Since there is no output schema, the summary of returned fields (price, 24h change, market-cap rank) does real work. Only the precise response shape and refresh cadence are unstated.

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 and the input schema is an empty object, so there is nothing for the description to disambiguate. Baseline applies; the description correctly avoids inventing parameter guidance.

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 states a specific verb and resource pair in its second clause: it returns the 'live USD price, 24h change and market-cap rank' for USX. The tool name already encodes the asset, so an agent can identify what it does without opening the schema. It does not, however, distinguish itself from close siblings like buy_coin_USX or buy_crypto_price, which appear to cover similar ground.

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 implied rather than stated: an agent can infer 'call this when you need USX price data.' The phrase 'No account, no API key' reads as a prerequisite, not a when-to-use rule. There is no explicit guidance on when to prefer this over buy_coin_USX or buy_crypto_price, and no exclusions.

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