Crypto, web, finance and app data tools

evm_gas_fees

Current gas fees on Ethereum, Base, Arbitrum, Optimism or Polygon: base fee and slow/standard/fast priority and max fee in gwei plus the cost of a plain transfer. Use before sending a transaction.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "<chain>"
    },
    "name": "evm_gas_fees"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. It usefully states that results are 'current' and itemizes the returned fee components, but it says nothing about freshness/refresh cadence, whether unsupported chain values error out, or any rate limiting. For a read-only data tool this is acceptable but leaves gaps.

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?

Two tight sentences: the first front-loads what is returned, the second front-loads the usage cue. Every clause earns its place with no filler.

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?

An output schema exists, so return values need not be explained, yet the description still summarizes them usefully. It covers chains, units (gwei), fee tiers, and the transfer-cost estimate, leaving only the exact accepted chain-string format unspecified.

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?

Schema description coverage is 0% and there is no enum on the single 'chain' parameter, but the description enumerates the five valid chains, which is exactly the missing information. It does not specify the exact string format expected (e.g., lowercase vs. display name), which is a minor residual ambiguity for the only required parameter.

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 resource (current gas fees) and explicitly enumerates the supported chains (Ethereum, Base, Arbitrum, Optimism, Polygon) plus exactly what fields are returned. No sibling tool covers gas or EVM data, so separation is trivially clear and the verb/resource pairing is unambiguous.

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?

It gives a concrete usage cue: 'Use before sending a transaction,' which tells the agent when this tool is relevant. It does not name exclusions or alternatives, but no sibling tool is a plausible substitute, so the guidance is sufficient without being exhaustive.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?