Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FEUSD

Paid. Felix feUSD (FEUSD) 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/FEUSD.

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying endpoint URL. It stops short of describing response shape, latency, or freshness/caching semantics beyond calling the price 'live'.

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?

Terse and front-loaded: the asset and payload come first, then cost, then access terms, then the URL. Every clause carries distinct operational information; the only mild redundancy is restating 'FEUSD' twice in the opening line.

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-annotation, no-output-schema price fetch, the description covers what matters: what data comes back, what it costs, how to pay, and that there is no auth. It is slightly thin on error/failure semantics and output format, but the listed return fields largely substitute for a missing output schema.

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 nothing for the description to disambiguate; per the baseline this warrants a 4. It correctly implies the asset is baked into the endpoint (URL contains /price/FEUSD) rather than passed as an argument, which prevents an agent from hunting for a symbol parameter.

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 pair: fetches the Felix feUSD (FEUSD) USD price, and enumerates the returned fields (live USD price, 24h change, market-cap rank). The ticker-scoped name plus this sentence makes the target asset unambiguous among the hundreds of buy_tok_* siblings, though it never explicitly contrasts itself with generic siblings like buy_crypto_price.

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 rather than stated: an agent can infer this is the FEUSD-specific price purchase, but there is no explicit when-to-use/when-not or routing rule versus buy_crypto_price, buy_coin_FEUSD, or other overlapping price siblings. The payment terms are given, which frames the cost decision, but selection guidance 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