Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_crypto_gas_fee_estimator

Estimate live gas prices and USD transaction costs for transfers, ERC-20 transfers, and token trades across EVM chains including Base, Ethereum, Arbitrum, and Optimism.

Instructions

[On-Chain Intelligence] Live gas price and USD cost estimates for transfers, ERC-20 transfers and token-trade contract calls on EVM chains Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://crypto.caelaralabs.com.

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": "caelara_crypto_gas_fee_estimator"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain: base|ethereum|arbitrum|optimism (default base)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does contribute useful operational context: measured p50 12 ms / p95 14 ms latency with a benchmark source and date, plus the backing endpoint. It does not disclose rate limits, error behavior, or what the returned estimate covers (which transfer types get priced, whether USD cost requires an amount input), leaving real gaps for a pricing tool.

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?

Two compact sentences with the core capability front-loaded, followed by performance provenance. The bracketed category tag and the benchmark citation are mild marketing overhead, but nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no annotations and no output schema, the definition establishes purpose, scope, and latency adequately. It remains unclear what an estimate result looks like (gas price units, whether a USD figure is returned without an amount, per-chain differences), which is exactly the gap an absent output schema leaves the description to fill.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single optional 'chain' parameter, listing base|ethereum|arbitrum|optimism plus the default. The description only reinforces the EVM scope and adds no syntax, default, or behavioral nuance beyond the schema, so the baseline 3 applies.

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?

The description names a specific resource and capability: live gas price plus USD cost estimates for native transfers, ERC-20 transfers, and token-trade contract calls, scoped to EVM chains. That is far more specific than a label restatement, and none of the listed siblings cover gas pricing. It stops short of explicitly contrasting itself with alternatives, so a 4 rather than 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 implied by the enumerated use cases (transfer, ERC-20 transfer, contract call cost estimation) and the EVM-only scope, which implicitly excludes Solana-side siblings. There is no explicit when-to-use/when-not guidance, no note on whether estimates are live-only versus historical, and no pointer to a related tool such as the token price aggregator for converting amounts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools