Skip to main content
Glama

Caelara Labs On-Chain Intelligence

gas_fee_estimator

Live gas price and USD cost estimates for transfers, ERC-20 transfers and swaps on EVM chains

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and leaves key traits unstated: it is implicitly a read-only lookup, but there is no mention of external RPC/API dependency, rate limits, staleness, or the return shape (one estimate vs. one per operation type). Most notably, it promises 'USD cost estimates' without any amount or gas-limit parameter, so it is unclear what transfer size the USD figure assumes.

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?

A single front-loaded sentence with no redundant wording; the scope (live, USD, operation types, EVM) is packed efficiently. It is arguably too terse given what it omits, but nothing in it is wasted.

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-optional-parameter, no-output-schema tool, the description covers what is estimated and where, which is close to sufficient. It still leaves an agent guessing what the USD estimate is based on (transfer size, gas limit) and whether multiple estimates come back at once.

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?

The single optional parameter has 100% schema coverage, including a default and an enumerated chain list, so the schema already does the work. The description adds nothing beyond 'EVM chains' — it does not explain that omitting chain defaults to base or how chain selection affects the returned cost estimates, so 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 concrete resource (gas price and USD cost estimates) and scopes it to 'transfers, ERC-20 transfers and swaps on EVM chains', so an agent knows exactly what it returns. It does not explicitly differentiate from any sibling, but no sibling in the list overlaps this domain, so the gap is minor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no named alternatives or exclusions. 'Live' hints at a real-time lookup versus a cached/historical source, but nothing tells an agent when to prefer this over, say, token_price_aggregator for cost figures.

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