Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CFX

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With zero annotations, the description carries the full behavioral burden and does a good job: it discloses that calls are metered ($0.01 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged — the exact cost-risk facts an agent needs before spending. It does not cover rate limits, latency, or data freshness, which keeps it at a 4.

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?

Two compact sentences, front-loaded with the payment flag and the data payload, followed by cost mechanics and the endpoint URL. Every clause carries a distinct decision-relevant fact; nothing is padded.

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 price lookup, the description supplies what the schema cannot: what fields come back, what it costs, where the payment settles, and that failures are free. It falls just short on freshness/latency expectations and on clarifying the overlap with buy_coin_CFX.

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, so there is no parameter meaning to add and the baseline of 4 applies. The description instead spends its words on what the response contains (price, 24h change, market-cap rank), which is the useful substitute.

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 and resource: live USD price of Conflux (CFX) with 24h change and market-cap rank. An agent knows exactly what data comes back. It does not, however, distinguish itself from the sibling buy_coin_CFX, which appears to cover the same token from a different endpoint family — that ambiguity is the only thing keeping this from a 5.

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?

The usage context is implied well enough (call this when you need CFX spot/24h data), and the payment terms signal it is a paid alternative to any free source. There is no explicit when-to-use/when-not guidance and no pointer to buy_coin_CFX or buy_crypto_price as alternatives, so an agent facing 500+ siblings has no stated routing rule.

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