Axiom Agentic Tools

Base Gas Tracker

base-gas-tracker

Read-only

Live Base network gas tracker. Returns current gas price in gwei, base fee, priority fee (tip), and a block history showing recent gas trends. Useful for timing transactions and estimating costs. $0.01/call.

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": "base-gas-tracker"
  }
}

Input Schema

Name	Required	Description	Default
`blocks`	No	Number of recent blocks to include in history (1-20, default 10)

Output Schema

Name	Required	Description	Default
`trend`	Yes
`fetched_at`	Yes
`base_fee_gwei`	Yes
`block_history`	Yes
`gas_price_gwei`	Yes
`priority_fee_gwei`	Yes
`max_fee_suggestion_gwei`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedJun 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable context: it is a 'live' feed, lists exact return fields, and discloses the $0.01/call cost. No contradictions with annotations.

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?

Four sentences, each earning its place: identifies the tool, enumerates outputs, states use cases, and discloses cost. No redundant or filler content.

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

Completeness5/5

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

For a single-optional-parameter tool with a rich output schema and annotations, the description fully covers purpose, return content, use case, and cost. It is complete and well-rounded.

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 coverage is 100% with full description of the 'blocks' parameter. The description does not add parameter-specific detail, but the schema already handles it. No extra value needed beyond the baseline.

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?

The description clearly states a specific verb ('Returns') and resource ('Base network gas'), enumerating the exact data fields (gas price, base fee, priority fee, block history). It is inherently distinct from all sibling tools, which address unrelated domains.

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?

Provides clear context on when to use the tool ('timing transactions and estimating costs'), but does not explicitly mention when not to use it or reference alternatives. Given the uniqueness among siblings, this is adequate guidance.

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

All Axiom Agentic Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.