Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Gas tracker, multichain gas: 5 EVM chains and Bitcoin fees

pack_gas_tracker
Read-only

One call for current gas prices on Base, Ethereum, Arbitrum, Optimism and Polygon: gas price, base fee and priority fee in gwei and what a plain transfer costs in the native coin and in US dollars (Uniswap prices), sorted cheapest first, plus Bitcoin fee rates in sat/vB. Cheaper than the tools bought one by one. Use to pick the cheapest chain, time a transaction or show fees in a wallet. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
onlyNoOptional: comma-separated top-level result keys to keep, for a smaller answer (for example only=price,symbol); unknown keys are ignored and an empty match returns the full result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so 'Reads or computes only and changes nothing' is mostly redundant. The genuine added value is the billing model: $0.002/call via x402 USDC or a card key, first 25 free, failed calls free, and 'each call is charged, so repeats are not free', which explains the non-idempotent behavior a caller would otherwise only infer from idempotentHint=false. The data source (Uniswap prices) and cheapest-first ordering are also disclosed; only the response shape is left implicit.

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?

The capabilities and return fields are front-loaded before pricing and use-case notes, and no sentence is pure filler. Minor waste remains in 'Reads or computes only and changes nothing', which restates readOnlyHint, and the pricing clause is dense but each element (price, payment options, free tier) is decision-relevant.

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?

With no output schema and a single trivial parameter, the description carries the return-value burden and does so: it lists the fee fields, the fiat/native cost, the sort order and the Bitcoin units. It falls slightly short by not sketching the per-chain result structure (e.g. what keys the 'only' filter can target), which would help a caller use the one parameter it exposes.

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 description coverage is 100% and the single optional 'only' filter is fully documented in the schema, including its comma-separated format and unknown-key behavior. The description never mentions the parameter, so it adds no meaning beyond the schema; the baseline 3 applies.

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 names a concrete verb and resource ('One call for current gas prices') and enumerates exactly what is returned per chain: gas price, base fee, priority fee in gwei, plus transfer cost in native coin and USD, and Bitcoin fee rates in sat/vB. That scope statement is enough to separate it from the single-chain siblings like eth_gas, arb_gas and btc_fees without opening any schema.

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?

It gives three concrete use cases ('pick the cheapest chain, time a transaction or show fees in a wallet') and implicitly positions itself against the per-chain tools ('Cheaper than the tools bought one by one'). There is no explicit when-not guidance or named alternative for someone who only needs one chain's fee, so it stops short of a 5.

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.