Skip to main content
Glama

Genexxis paid agent tools (x402)

gas_now

Current gas on one EVM chain: base fee and slow/standard/fast priority fee in gwei, and USD cost of a native transfer, an ERC-20 transfer and a Uniswap swap including the L1 data fee on rollups. Price: $0.002 USDC per call, paid with x402 on Base.

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

Input Schema

NameRequiredDescriptionDefault
chainYesethereum, base, arbitrum, optimism, polygon or bsc

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the two things an agent most needs: the output payload composition and that each call costs $0.002 USDC via x402 on Base. It does not mention freshness/latency or failure modes, keeping it short of a 5.

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, front-loaded with the resource and its payload, with the payment terms as a separate trailing sentence. Nothing is redundant or padded.

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?

There is no output schema and no annotations, so the description must describe the return values itself – which it does in detail, including the L1 data fee on rollups. Pricing is also covered, so an agent has everything needed to decide and call.

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 the single chain parameter already lists the six accepted values, so the schema does the heavy lifting. The description only reiterates 'one EVM chain' without adding format or default guidance beyond the schema.

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?

The description states a specific resource ('current gas on one EVM chain') and enumerates exactly what is returned: base fee, slow/standard/fast priority fees, and USD cost of native/ERC-20/Uniswap transactions. It is clear what the tool does, but it never names gas_compare, so an agent must infer the single-chain vs comparison split.

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?

'on one EVM chain' hints that this is the single-chain variant as opposed to the gas_compare sibling, but the routing is left implicit rather than stated. No prerequisites or exclusions are given beyond the price note.

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