Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FXUSD

Paid. f(x) Protocol fxUSD (FXUSD) 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/FXUSD.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 well: it discloses that the call is paid, the exact price and accepted payment rails ($0.05 USDC on Base or Solana), that no account or API key is required, and the failure-billing policy ('Failed calls not charged'). Not covered: rate limits, latency, or what a payment failure looks like, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly 30 words, front-loaded with the 'Paid.' flag so cost is known before anything else, then payload, then price/rails, then auth and billing. Every clause carries distinct information, and the endpoint URL is the only arguable extra, but it is a single token of text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter single-value lookup with no output schema, the description covers what is returned, what it costs, how to pay, and what happens on failure — everything an agent needs to decide and execute. Nothing material is missing at 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 and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly avoids inventing parameter discussion.

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 resource and provider ('f(x) Protocol fxUSD (FXUSD) price') and enumerates what comes back: live USD price, 24h change, market-cap rank. That is more specific than the tool name alone, which only carries the ticker. It does not distinguish itself from the hundreds of sibling buy_tok_* / buy_coin_* tools, so an agent gets no routing signal beyond 'this is the FXUSD one'.

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 context is implied rather than stated: you call it to get FXUSD pricing. Useful preconditions are present (paid, no account, no API key), but there is no statement of when to prefer it over buy_crypto_price, buy_coin_* or other token endpoints, and no exclusions or prerequisites for the payment flow.

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