Skip to main content
Glama

polygon-fee-snapshot

Polygon PoS fee reference. A static snapshot captured 2026-11-14, no input: the EIP-1559-style fee mechanics with the mandatory 25 gwei minimum priority fee, the observed 30-100 gwei typical base-fee band with the 2026 monthly averages, and transfer and swap cost scenarios computed at the band edges and the reference POL price, 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": "polygon-fee-snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so unusually well: it discloses the fixed capture date (data staleness), that the capture date is printed on every card, the exact cost ($0.01/call in USDC on Base via x402), and the failure mode (HTTP 402 with machine-readable terms). The only gap is it doesn't say how recently the snapshot should be considered valid or what happens after payment failures.

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?

Every clause adds value — contents, capture date, price, payment protocol, and error behavior — and the purpose is front-loaded. However, the middle section is a single dense run-on clause enumerating the card contents, which slows scanning compared to a short list.

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?

Completeness is strong for a zero-param tool: it enumerates the returned content (EIP-1559 mechanics, 25 gwei priority floor, 30-100 gwei base-fee band, 2026 monthly averages, transfer/swap scenarios at band edges, capture date) even though no output schema exists. Minor gap: it doesn't describe structure (e.g., one card vs a collection) or whether the POL price reference dominates the scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, and the description explicitly states "no input", so the agent knows it can call immediately with an empty object. There is no ambiguity to resolve beyond what the schema already shows.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete resource ("Polygon PoS fee reference") and immediately qualifies it as a static snapshot, so the agent knows exactly what it retrieves and that it is chain-specific. It does not explicitly contrast itself with the sibling chain snapshots (arbitrum/base/ethereum/optimism-fee-snapshot), leaving that differentiation to the name.

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?

The "no input" and "static snapshot captured 2026-11-14" framing implies the appropriate use case — reading a fixed fee reference rather than live chain data — but the description never states when to choose it over alternatives or warns against relying on it for current fees. Guidance is implied rather than explicit.

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