Skip to main content
Glama

gas_price

Read-only

Retrieve the current Ethereum network fee rate in Gwei to estimate transaction costs without an API key.

Instructions

Get the current gas price in Gwei. Public; no API key required.

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_price"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint=true already establishes this as a safe read, so the description's added value is the auth disclosure: public and keyless. It does not say whether the value is cached, how fresh it is, or whether it returns a single number vs. slow/standard/fast tiers, which are the remaining behavioral unknowns for a gas oracle.

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 short sentences with zero filler; the core action and unit come first and the access note follows. Every clause earns its place.

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 zero-parameter read with no output schema and a readOnly annotation, the description is nearly sufficient: it names the resource, the unit, and the auth posture. The one meaningful omission is the shape of the returned value (single price vs. multiple speed tiers), which would affect how the agent interprets the result.

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?

The tool takes zero parameters, so the baseline is 4 regardless of schema coverage. The description usefully fixes the output unit as Gwei, adding a small amount of meaning not present in an empty 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?

States a specific verb and resource ("Get the current gas price") and pins down the unit (Gwei), so the agent knows exactly what value comes back. It does not name a sibling, but none of the listed siblings (balance, wallet, transaction, address tools) overlap with gas pricing, so differentiation is largely moot.

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?

Gives clear access context ("Public; no API key required"), which tells the agent it can call this without credentials or setup. There is no explicit when-to-use or when-not-to-use statement, but with no competing gas-related sibling the only open question — prerequisites — is answered.

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