Skip to main content
Glama

arbitrum-fee-snapshot

Arbitrum One fee reference. A static snapshot captured 2026-11-14, no input: the two-dimensional fee model (the L2 execution floor at 0.1 gwei, the adaptive parent-chain calldata fee priced by Brotli-compressed size), the floor-price transfer scenario computed at the floor, and the observed 2026 typical transfer range, the capture date printed on every card. Price: $0.01 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "arbitrum-fee-snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it states the data is a static snapshot captured on 2026-11-14, requires no input, costs $0.01 per call in USDC on Base over x402, and explains that unpaid calls return HTTP 402 with machine-readable payment terms.

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 description is front-loaded with the resource type and snapshot nature, then lists returned data and payment behavior. It is efficient with no wasted sentences, though the dense list of fee-model details and parentheticals makes it somewhat harder to scan than a more structured version would be.

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?

There is no output schema, so the description must explain returned content -- and it does: fee model components, transfer scenario, typical range, and capture date. It also covers the paid-call behavior and HTTP 402 fallback, making it complete enough for an agent to invoke correctly.

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 has zero parameters, so the baseline is 4. The description confirms 'no input', which is the only parameter-relevant semantics needed for a zero-parameter snapshot tool.

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 identifies a specific resource -- an Arbitrum One fee reference -- and enumerates its contents: the L2 execution floor, adaptive calldata fee, floor-price transfer scenario, observed transfer range, and capture date. The chain name also clearly differentiates it from sibling fee snapshots for Base, Ethereum, Optimism, and Polygon.

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?

Usage is implied by 'Arbitrum One fee reference' and 'no input', making it clear this is a static lookup for Arbitrum fees. However, the description does not explicitly say when to choose this over sibling chain snapshots or when it may be inappropriate, so guidance is only implicit.

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