Multi-chain gas prices in one call -- ETH, Base, Polygon, Arbitrum, BSC. Compare chains to find cheapest.
Single tool 'crypto_estimate_gas' has a detailed description (340+ chars) but critical schema deficiencies. Input schema is present but lacks proper type definitions for the 'chain' parameter, it declares type 'string' with only a description, no enum constraint despite listing exactly 5 valid values (ethereum, base, polygon, arbitrum, bsc). Output schema is documented in the description text but NOT in a formal JSON Schema structure. Parameter lacks minimum/maximum constraints. No error handling guidance. Tool naming is acceptable (verb_noun pattern) but schema incompleteness and missing output schema definition are major gaps for production use.
Use this when you need to compare gas prices across multiple EVM chains at once. Returns multi-chain gas estimates in JSON. 1. chains: array of chain gas data with chain name 2. low: gas price in gwei for slow confirmation 3. medium: gas price in gwei for standard confirmation 4. high: gas price in gwei for fast confirmation 5. transferCostUsd: estimated USD cost for a simple transfer on each chain 6. cheapestChain: which chain currently has the lowest gas cost Example output: {"chains":[{"chain":"base","low":0.005,"medium":0.008,"high":0.012,"transferCostUsd":0.01},{"chain":"ethereum","low":12.5,"medium":18.0,"high":25.0,"transferCostUsd":0.85}],"cheapestChain":"base"} Use this FOR choosing the cheapest chain before a cross-chain transaction. Essential for multi-chain agents that need to optimize gas costs. Do NOT use for single-chain gas only -- use gas_get_current_price instead. Do NOT use for swap quotes -- use dex_get_swap_quote instead. Do NOT use for bridging -- use bridge_find_best_route instead.
Input parameter 'chain' lacks enum constraint despite documentation listing exactly 5 valid values (ethereum, base, polygon, arbitrum, bsc). LLMs will hallucinate invalid chain names instead of selecting from the constrained set.
Output schema is documented only in prose description, not as a formal JSON Schema. LLMs cannot parse the expected response structure (chains array, low/medium/high fields, transferCostUsd, cheapestChain) from text alone. Must define outputSchema in tool registration.
No error handling guidance. Tool description does not explain what happens if an invalid chain is passed, if the API is unavailable, or if gas data is stale. LLMs have no recovery path on failure.
Parameter 'chain' is optional but behavior when omitted is unclear. Description says 'Omit for all chains' but does not specify the response structure when multiple chains are returned vs. a single chain.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2025-06-18+ | v2 |
Tool description includes example output values in prose (e.g., 'base', 'ethereum', '0.005', '12.5') which LLMs may reuse literally in subsequent calls rather than adapting to real data. Use formal schema constraints instead.