Skip to main content
Glama

Gas Oracle

gas_oracle
Read-onlyIdempotent

[$0.01 USD per call] Live gas prices (gwei) for Ethereum, Base, Polygon. Live-RPC sourced, no key required.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gas_oracle"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoOptional x402 payment proof (EIP-3009 signed authorization). Call once without it to receive the payment requirements, then retry with the proof.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety bar is low; the description adds genuinely new context by disclosing the $0.01 per-call cost and that data comes from live RPC with no API key. It stops short of describing the response shape (e.g. one value per chain), which is the only remaining behavioral gap.

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 compact sentences with the price caveat front-loaded before the capability statement, and no filler. Every clause (cost, unit, chains, source, no key) carries information an agent needs.

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 read-only, zero-required-parameter tool with a well-documented optional payment param and no output schema, the description covers cost, auth model, chains and units. Only the return format across the three chains is left to inference.

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?

There is a single optional parameter at 100% schema description coverage, and the schema fully explains the x402 payment-proof handshake. The description adds nothing beyond that, which fits the baseline-3 rule when the schema already does the work.

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 the specific resource (live gas prices), the unit (gwei), and the exact scope (Ethereum, Base, Polygon), plus the data source. None of the sibling tools overlap with gas pricing, so an agent can identify this tool unaided.

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 rather than stated: an agent can infer it should call this when it needs current gas costs, and 'no key required' plus the price line signal it is a cheap read. There is no explicit when-not-to-use or named alternative, so guidance stays implicit.

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.