Skip to main content
Glama

EIP-7702 Smart-Wallet, Passkey Session Key & Gas-Optimizer MCP

Compare Live Multi-Chain EVM Gas Fees & Route to Cheapest Execution L2

optimize_multichain_evm_gas_routing
Read-onlyIdempotent

Queries live eth_gasPrice across Base, Optimism, Arbitrum, Polygon, and Ethereum to rank exact USD gas cost per swap and recommend the lowest-fee execution chain.

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

Input Schema

NameRequiredDescriptionDefault
txGasUnitsNoEstimated gas units for the transaction (default 180000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the description's job is to add operational context, and it does: it discloses the live RPC method used (eth_gasPrice), the exact five chains queried, and that costs are normalized to USD. Remaining gaps are latency, rate limits, and whether the chain list is fixed, which matter for an openWorldHint tool but are secondary.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with zero filler, front-loading the action (queries) and the chain set before the outcome (rank USD cost, recommend the cheapest chain). Every clause carries information an agent needs to select the tool.

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 one-optional-parameter, read-only tool with rich annotations and no output schema, the description covers what is queried and what is returned (a USD cost ranking plus a recommendation), which is the minimum an agent needs. It stops short of describing the response structure or freshness guarantees (e.g., whether prices are spot or cached), which would matter since no output schema exists.

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 description coverage is 100% and there is only one optional parameter (txGasUnits) with a documented default of 180000, so the schema does the heavy lifting and the baseline applies. The description never mentions txGasUnits at all, adding no meaning beyond the schema — notably it does not explain that gas cost scales linearly with the supplied unit estimate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (queries live eth_gasPrice), an explicit resource scope (Base, Optimism, Arbitrum, Polygon, Ethereum), and the two outputs it produces: a USD cost ranking per swap and a cheapest-chain recommendation. That is far more than a restatement of the name; an agent can distinguish this from every sibling, none of which performs cross-chain fee comparison.

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: the mention of 'per swap' and 'recommend the lowest-fee execution chain' suggests calling it before routing a transaction. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., plain single-chain gas lookup), so an agent must infer the point in the workflow where this belongs.

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.