Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FOGO

Paid. Fogo (FOGO) 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/FOGO.

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

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 present, the description carries the full burden and does a solid job: it discloses that the call is paid, the exact cost ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — the failure/refund policy is exactly the kind of detail annotations would otherwise supply. It omits data freshness (how 'live' the price is), source/exchange, and latency, 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 the single most decision-relevant token, 'Paid.', followed by tightly packed clauses with no filler. The bare endpoint URL is arguably dead weight for a zero-parameter tool, but it is the only slightly non-earning element in an otherwise dense definition.

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, the description must convey both what comes back and what it costs; it does both (price, 24h change, market-cap rank; $0.01 USDC with no charge on failure). The remaining gap is provenance and refresh cadence, which matters for a price feed but is not stated.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema is empty and fully consistent with the description's claim that only the URL/symbol identifies the request.

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 resource and payload: 'Fogo (FOGO) price: live USD price, 24h change and market-cap rank.' The symbol-specific tool name plus the quoted fields make it unambiguous which asset is priced. It never names how it differs from adjacent siblings such as buy_coin_FOGO or the generic buy_crypto_price, so it stops short of 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?

Usage is only implied by the subject matter — an agent infers 'call this when you need the FOGO spot price.' There is no explicit when-to-use, when-not-to-use, or pointer to an alternative for other tokens or for broader market data. The payment and failure clauses describe conditions of calling, not selection guidance.

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