Skip to main content
Glama

L2 gas

l2_gas_intelligence
Read-only

Compare gas costs across 8 L2 chains in real time. Returns gas price in Gwei, estimated swap cost in USD, cheapest/most expensive chain, and a recommendation. Queries all L2 RPCs in parallel. Costs $0.002 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds real value: it discloses that all L2 RPCs are queried in parallel (latency/aggregation behavior) and states an explicit cost of $0.002 USDC per call, which is not captured anywhere in structured fields. It stops short of describing failure behavior when an RPC is unreachable.

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?

Three short sentences, front-loaded with purpose, followed by return contents, execution behavior, and cost. Every sentence carries distinct information with no repetition.

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?

With no output schema and no parameters, the description carries the burden of explaining returns and does so by listing Gwei price, USD swap cost, cheapest/most expensive chain, and a recommendation. It is complete enough for invocation; only edge-case behavior (partial RPC failures, which chains) is left unstated.

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, so per the baseline this scores 4. The description correctly adds no parameter detail, and nothing about the empty schema is misrepresented.

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 verb and resource ('Compare gas costs across 8 L2 chains in real time') and enumerates what is returned. It is clear what the tool does, but it never distinguishes itself from the sibling gas_tracker, leaving the agent to infer the scope difference.

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 description (multi-chain L2 gas comparison), but there is no explicit when-to-use guidance, no exclusion, and no named alternative such as gas_tracker for single-chain or mainnet gas. The agent must infer the selection rule.

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