Skip to main content
Glama

MCPFax On-Chain Toolkit

by com.mcpscores
OverviewDiscussionsAdmin

Current gas price on one or several chains

gas_now

Live gas price on Ethereum, Base, Arbitrum, Optimism or Polygon — in wei and gwei, plus what a plain 21,000-gas transfer would cost in the native token, which is the number you actually budget with. Pass several chains comma-separated to compare where to execute. Call this immediately before sending a transaction: gas moves every block, so the answer is good for seconds, not minutes. Costs $0.005 USDC per call via x402 on Base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoOne or more of ethereum, base, arbitrum, optimism, polygon — comma-separated, e.g. 'base,ethereum'. Defaults to base.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / chain / examples
      Added value: +[
+  "base"
+]
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

No annotations provided, but description fully discloses output details (wei, gwei, transfer cost) and the per-call fee of $0.005 USDC. No hidden side effects or contradictions.

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?

Though slightly long, every sentence adds value—purpose, units, usage timing, and cost. Logical flow from function to specific details makes it efficient without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description specifies exactly what data is returned (wei, gwei, transfer cost) and what it represents. Full parameter defaults and usage scenarios covered, leaving no gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'chain' parameter is thoroughly explained with accepted values (Ethereum, Base, Arbitrum, Optimism, Polygon), comma-separated usage, example, and default. 100% schema coverage ensures full clarity.

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?

Clearly states it provides live gas price for multiple chains with specific units (wei and gwei) and includes transfer cost estimation. Distinct from sibling tools that focus on address, demand, tokens, etc.

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

Usage Guidelines5/5

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

Explicitly instructs to call immediately before sending a transaction due to fast gas moves, and explains how to pass multiple chains for comparison. Also mentions cost per call, giving clear timing and context.

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

All MCPFax On-Chain Toolkit toolsInspect
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