Skip to main content
Glama

get_gas_price

Current Base mainnet gas price in Gwei.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose that the value is a live/current reading scoped to Base mainnet and denominated in Gwei. It says nothing about freshness/caching behavior, whether the number is a base fee or suggested priority-inclusive price, or failure modes when the RPC is unreachable.

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?

One short, front-loaded phrase with zero filler or repetition, and the network qualifier is placed directly after the resource. It is a sentence fragment rather than a full statement, but nothing could be cut without losing information.

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 annotations and no output schema, the description covers the essentials: what is measured, on which chain, and in which unit — effectively standing in for the missing return-value documentation. The remaining gap is precision/scope of the price (base fee vs. effective gas price), which matters for fee estimation.

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 of 4 applies; there is no parameter meaning to explain. Nothing in the description misrepresents the empty input 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 the resource (gas price), the network (Base mainnet), and the unit (Gwei) in a single phrase, so an agent can tell it apart from sibling reads like get_eth_balance or get_block_number. It lacks an explicit verb (e.g., 'returns'/'fetches'), which is the only thing keeping it below a 5.

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?

No when-to-use guidance is given: nothing says whether this is for live transaction-fee estimation versus historical queries, and no alternative tool is named. The word 'Current' hints at a live snapshot but the agent must infer it.

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