Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FRAX

Paid. Legacy Frax Dollar (FRAX) 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/FRAX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 burden and discloses the key traits: it is a paid call, priced at $0.05 USDC on Base or Solana, needs no account or API key, and failed calls are not charged. It still says nothing about payment flow mechanics, latency, or rate limits, so it stops short of full transparency.

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?

Information is front-loaded and dense: asset and data payload first, then price, payment rails, signup requirements, and failure policy, closing with the endpoint URL. The clipped 'Paid.' opener and the bare URL are slightly awkward but every sentence carries operational value.

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 paid price lookup with no output schema, the description covers what is needed to call and budget for it: data returned, price, payment chains, and failure billing. It lacks only finer return-format or freshness details, which are minor at this complexity.

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 no parameters (required: [], properties: {}), so there is no schema surface needing explanation; the baseline for zero-param tools applies. The description correctly avoids inventing parameter details and instead spends its words on cost and coverage.

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?

The description names a specific verb and resource ('Frax Dollar (FRAX) price'), scopes it ('live USD price, 24h change and market-cap rank'), and the 'Legacy' qualifier distinguishes it from current-asset price siblings. An agent can tell what it returns without inspecting anything else.

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 by the paid model and the fixed FRAX scope, but there is no explicit when-to-use or when-not-to-use guidance. It does not state how this differs from neighboring token-price tools (e.g. buy_coin_FRAX or buy_stable_frax) for legacy vs current FRAX, leaving that selection to inference.

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