Get the current Base network gas price in gwei and wei, plus the estimated cost of a standard 21k native transfer, to budget transactions before sending.
Current base gas price (gwei + wei) and estimated cost of a 21k native transfer. Pay-per-call ($0.005 USDC).
| Name | Required | Description | Default |
|---|---|---|---|
| fields | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the burden. It does disclose a meaningful behavioral fact beyond the schema: the call is paid per request ($0.005 USDC). However, it does not mention authentication, rate limits, response behavior, or side effects, so coverage is partial.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded with the core result, and the per-call pricing note is useful and non-redundant. A minor point is lost because the chain name could be made more explicit for an agent selecting among chain-specific siblings.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema, one undocumented optional parameter, and no annotations, the description is too thin. It tells the agent what data is returned and the cost, but not the meaning of the fields parameter, network identification, or relationship to sibling gas tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has one parameter, fields, with no schema description, and the description does not explain what fields accepts or how it affects the response. With 0% schema description coverage, the description needed to compensate but does not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific output: current base gas price in gwei and wei, plus estimated cost of a 21k native transfer. This distinguishes it from sibling tools like base_health or base_balance, though it does not explicitly differentiate it from polygon_gas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives. The description implies a gas-price use case but does not explain when to choose base_gas over polygon_gas or other network-specific tools, leaving selection to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.