Skip to main content
Glama

gas_oracle

Read-onlyIdempotent

Current gas prices (slow/standard/fast) for any supported EVM chain with trend analysis.

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

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain networkethereum

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description's only added behavioral claim is 'trend analysis', which hints at extra returned data but never says what the trend covers or over what window, and says nothing about price freshness or caching.

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?

A single front-loaded sentence that leads with the deliverable (current gas prices) and the tiers, with no filler. The trailing 'with trend analysis' is the one loosely specified fragment, but nothing is redundant.

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

Completeness3/5

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

The tool is simple with one optional, defaulted parameter and rich annotations, so the description is close to sufficient. However, with no output schema, the vague 'trend analysis' phrase is the only hint at return shape and leaves the agent guessing about what trend data comes back.

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 parameter is an enum with a default, so the schema already carries full meaning. The description's 'any supported EVM chain' adds no syntax or format detail beyond it, making the baseline 3 appropriate.

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 names a specific resource and the exact data returned: current gas prices in slow/standard/fast tiers, plus trend analysis, scoped to EVM chains. No sibling tool covers gas pricing, so differentiation is implicit rather than stated, and 'any supported EVM chain' is looser than the six-value enum in the schema.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when another tool (e.g. tx_simulate or trade_check, which also touch gas costs) would be preferable, and no prerequisites or caveats. An agent can infer the use case from the name, but the description contributes nothing beyond that inference.

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.