Skip to main content
Glama

FabTally Chain

by io.github.zvmzaretsky

Current gas for a chain (paid $0.001)

gas

PAID $0.001 (x402, USDC on Base). Current gas for a chain via public RPC: base fee + suggested priority + suggested max fee (gwei) at the latest block. If below_gwei is set, also returns whether the base fee is at/below your threshold right now. Read-only. Args: chain (ethereum|base|arbitrum|polygon|bsc|optimism), below_gwei (optional). Without payment returns the x402 challenge; pass x_payment to settle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYesChain to read gas for.
x_paymentNox402 payment payload (base64) for this PAID read. If supplied it is forwarded as the X-PAYMENT header to settle the call and return the real result instead of a 402 challenge. Omit to get the price challenge first.
below_gweiNoOptional threshold: return a boolean of whether base fee is at/below this many gwei now.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description discloses essential behavior: it is read-only, requires payment, and returns a challenge when x_payment is omitted. It also explains the optional below_gwei threshold behavior. This covers the main behavioral aspects an agent needs to know.

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?

The description is compact, front-loaded with the paid status, and efficiently communicates the core function, payment flow, and optional threshold. Every sentence contributes useful information without redundancy.

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?

Given the absence of an output schema, the description adequately explains the return values (base fee, priority, max fee, optional boolean) and the payment challenge/settle mechanism. It provides enough context for an agent to understand the tool's full behavior.

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?

The input schema provides complete descriptions for all three parameters (chain, x_payment, below_gwei), achieving 100% coverage. The description reinforces the chain options and optionality but does not add substantially new semantic meaning beyond the schema.

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 the tool's purpose: returning current gas data (base fee, priority fee, max fee) for a supported chain via public RPC. It also specifies the output format (gwei) and an optional threshold check, making it distinct from sibling tools (ens_expiry, oracle_health, token_unlocks).

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 provides clear context on when to use the tool: for reading current gas prices. It explains the payment flow (x402 challenge vs. x_payment to settle), but does not explicitly mention alternatives or when not to use it, though the sibling tools are clearly different in scope.

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

All FabTally Chain toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct on-chain data category: ENS expiry, gas fees, oracle health, and token unlocks. There is no overlap in purpose or arguments, making selection unambiguous.

Naming Consistency5/5

All tool names follow a consistent snake_case format with descriptive nouns (ens_expiry, gas, oracle_health, token_unlocks). No mixed conventions or vague verbs are present.

Tool Count5/5

Four tools is a well-scoped size for a focused read-only blockchain data server. Each tool provides a distinct service without redundancy or unnecessary bloat.

Completeness4/5

The set covers common on-chain data needs (ENS, gas, oracles, token emissions), but could be more comprehensive by including e.g. block/transaction info or token balances. However, within its apparent niche it is reasonably complete.

Resources