Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FDUSD

Paid. First Digital USD (FDUSD) 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/FDUSD.

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

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 provided, the description carries the full burden and does well: it discloses the tool is paid, the exact price ($0.05 USDC), the accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and it gives the endpoint URL. Missing only lower-priority details such as rate limits, response format, or data freshness, which keeps it at a 4 rather than 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.

Conciseness4/5

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

The text is short and front-loaded, starting with 'Paid.' so the cost signal is unmissable, followed immediately by what data is returned. The URL at the end is slightly noisy for an agent that will not call it directly, but every other clause (price, chains, no account, no charge on failure) earns its place.

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?

There is no output schema, so the description must convey the return content, and it does by enumerating price, 24h change, and market-cap rank. Combined with payment rails, auth-free access, and failure billing policy, an agent has enough to decide and invoke correctly. Only the literal response shape (field names, formatting) is left unspecified.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly does not waste space inventing parameter guidance, and instead spends its text on cost and access information.

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 the specific resource (First Digital USD / FDUSD) and exactly what is returned: live USD price, 24h change, and market-cap rank. It is not merely a restatement of the name, but it does not distinguish this from the closely related sibling buy_stable_fdusd, leaving ambiguity about which FDUSD tool an agent should pick.

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 topic: an agent can infer it is for fetching FDUSD pricing. There is no explicit statement of when to prefer this over buy_stable_fdusd or the buy_coin_* family, and no mention of staleness or refresh cadence. The payment/access logistics are covered, but routing guidance vs alternatives is absent.

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