Skip to main content
Glama

get_base_gas

Paid $0.02 (x402, USDC Base): live Base gas — gas price, EIP-1559 base fee and suggested priority fee in Gwei. Tx cost planning for agents.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 it discloses the most consequential trait an agent needs: the call costs $0.02 via x402 in USDC on Base. It does not cover latency, caching, or failure behavior (e.g. what happens if payment fails), which keeps 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?

One dense sentence with the cost gate front-loaded, followed by the exact payload contents and the intended use case. No filler, no repetition of the name.

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-only oracle with no output schema, the description names the three returned fields and their units, which is enough to call it correctly. Minor gaps remain around data freshness and payment failure handling, but nothing essential is missing.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description wisely spends its words on return content and cost instead.

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?

States a specific resource (live Base gas) plus the exact values returned: gas price, EIP-1559 base fee, and suggested priority fee, with units (Gwei). This is clearly distinguishable from siblings like get_latest_block or get_crypto_price, which do not report gas fee components.

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?

"Tx cost planning for agents" implies the use context, but there is no explicit when-not guidance and no sibling alternative is named or excluded. An agent must infer that this is a read-only oracle call for fee estimation rather than being told so.

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