Skip to main content
Glama

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

Polygon block number

polygon_block
Read-only

Latest block number and block details on Polygon PoS, or any block by decimal number: hash, timestamp, transaction count, gas used and limit, base fee in gwei and producer. Use for timestamps and confirmation counts; for current fees use polygon_gas. A block that does not exist yet returns 422, uncharged. Example: number=latest. 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": "polygon_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberNoBlock number, or 'latest' (default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, openWorld and non-idempotent, and the description adds real context beyond them: 422 on missing blocks, uncharged failures, and per-call billing that makes repeats non-free (consistent with idempotentHint=false). Pricing detail ($0.002/call, 25 free, card key via /credits) is useful but edges toward commercial boilerplate rather than tool behavior.

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 core capability and the sibling routing are front-loaded in the first two sentences, and the edge case follows. The pricing/key paragraph is dense and slightly tangential to invocation but is short enough not to bury the lead.

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-parameter read tool with no output schema, the description covers return fields, the default, the error path, and billing consequences. There is no output schema to describe, so nothing material is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by specifying the number is decimal (not hex, which matters for EVM tooling) and by giving 'number=latest' as a concrete example of the default. That is a genuine clarification beyond the schema text.

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 opens with a specific verb+resource ('Latest block number and block details on Polygon PoS') and enumerates the returned fields (hash, timestamp, tx count, gas used/limit, base fee, producer). It also explicitly distinguishes itself from the fee sibling by naming polygon_gas, so an agent can separate it from the other chain-prefixed *_block tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use it ('for timestamps and confirmation counts') and names the alternative for the adjacent use case ('for current fees use polygon_gas'). It also flags an edge case up front: a nonexistent block returns 422 and is uncharged, so the agent knows how to handle the miss.

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.