Skip to main content
Glama

edge-signals

live_gas_before_submit

PRIMARY: Live gas fee snapshot before submitting an EVM transaction on Base (and Ethereum when configured). Returns maxFeePerGas and maxPriorityFeePerGas in gwei.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose that the tool is a read-only snapshot, that it returns gwei-denominated maxFeePerGas/maxPriorityFeePerGas, and that Ethereum support is configuration-dependent — but it says nothing about freshness/caching, whether an API key or chain config is required, or what happens when Ethereum is not configured.

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 tight sentences, front-loaded with the core purpose and followed by the return values. The leading "PRIMARY:" tag is meta-labeling that is never explained and adds a small amount of noise.

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 zero-parameter read tool with no output schema, the description covers purpose, chain scope, and the exact return fields with units. The remaining gap is operational detail: result staleness and failure behavior when the Ethereum chain is not configured.

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 there is nothing for the description to disambiguate; the schema is trivially complete. The stated gwei units and returned field names add useful meaning even without inputs.

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?

"Live gas fee snapshot" is a specific resource plus read action, scoped to Base and optionally Ethereum, and the description names the two returned fields. No sibling tool in the list covers gas pricing, so there is no ambiguity to resolve.

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

Usage Guidelines4/5

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

"before submitting an EVM transaction" gives a concrete usage moment rather than a vague hint. It stops short of stating exclusions (e.g. don't call when a fee was already supplied by the caller), but no comparable alternative tool exists to route away from.

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