Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FRXUSD

Paid. Frax USD (FRXUSD) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/FRXUSD.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 burden and does substantial work: it discloses the paid model and exact price ($0.01 USDC on Base or Solana), that no account or API key is required, that failed calls are not charged, and the literal endpoint URL. It stops short of describing the response payload format (JSON vs. text) or latency/rate behavior, which are the remaining unknowns for a purchase tool.

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?

Five short fragments, front-loaded with the cost signal 'Paid.' before the payload description, then commercial terms, then the endpoint. Nothing is padded and no sentence is redundant.

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?

With no output schema, no annotations, and no parameters, the description must explain what comes back and what it costs, and it does: price, 24h change, market-cap rank, plus payment rails and failure billing. Only the concrete response format is left unspecified, a minor gap for a zero-parameter read endpoint.

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 parameters such as a symbol or currency override.

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?

States a specific verb-resource pair: it returns the FRXUSD price with live USD price, 24h change, and market-cap rank, naming the exact token symbol. It does not explicitly distinguish itself from adjacent siblings such as buy_tok_FRAX, buy_stable_frax, or the generic buy_crypto_price, so an agent must infer the token identity from the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of the alternatives (buy_tok_FRAX, buy_coin_FRAX, buy_crypto_price) that could serve the same need. The payment and access notes are commercial context, not selection guidance, leaving the agent to infer that this is simply a single-asset price lookup.

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