Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TFUEL

Paid. Theta Fuel (TFUEL) 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/TFUEL.

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

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, the description carries the behavioral burden and does real work: it declares the tool is paid, quotes the exact price ($0.05 USDC) and accepted rails (Base or Solana), states no account or API key is required, and clarifies failed calls are not charged. It omits latency/data freshness and rate limits, which keeps it from 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?

Front-loaded with 'Paid.' followed by the data payload, then payment mechanics in one compact sentence. Every clause is informative; the raw endpoint URL is the only element of questionable value to an agent that invokes the tool by name.

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 tool this covers the essentials: what is returned (price, 24h change, market-cap rank), what it costs, how to pay, and the failure-billing policy. Only data freshness and response shape detail are missing.

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 the schema-semantics baseline is 4. Nothing in the description is needed to explain inputs, and nothing contradicts the empty schema.

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?

Names a specific resource (Theta Fuel / TFUEL) and the exact payload: live USD price, 24h change and market-cap rank. The verb is implicit in the naming convention, and the description never says how it differs from the generic sibling buy_crypto_price or the buy_coin_* family, so it falls short of 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?

Usage is only implied: an agent infers it should call this when it wants a TFUEL quote. In a sibling set containing buy_crypto_price and hundreds of per-asset variants, there is no explicit when-to-use or when-not rule, and no statement of alternatives.

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