Skip to main content
Glama

Block at time

block_at_time
Read-onlyIdempotent

Find the exact block number and timestamp at or before an ISO datetime or unix timestamp across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood). $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "<chain>",
      "time": "<time>"
    },
    "name": "block_at_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeYesISO datetime or unix seconds
chainYesethereum, base, arbitrum, optimism, polygon, bnb, arc or robinhood
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum, base, arc or bnb"New value: +"ethereum, base, arbitrum, optimism, polygon, bnb, arc or robinhood"
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses cost ($0.002 per call), accepted payment rails (USDC on Arc, Base or Solana, XNT on X1), and that the purchase settles inside the call once a signed payment is passed — exactly the auth/payment context annotations cannot convey. One tension remains: the call moves funds while readOnlyHint=true implies no side effects, so an agent must reconcile that itself. Return shape and no-match behavior are not described, but annotations already cover the safety profile.

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?

Three sentences, zero filler, and correctly front-loaded: purpose and scope first, price second, the payment handshake last. Each sentence carries distinct information an agent needs before calling.

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, the description does state what is produced (block number and timestamp), covers the supported chains and the full payment flow, so an agent can call it correctly. It is silent on edge behavior — e.g. what happens when no block exists at or before the given time — which is a minor remaining gap for a resolver tool.

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 coverage is 100%, so the schema already documents `time`, `chain`, and `payment`, and the baseline is 3. The description adds real value for `chain` (enumerating all eight supported networks) and for `payment` (how to obtain the signed payload via the two-step handshake), but adds no format nuance for `time` beyond what the schema says. Value is added, not transformative.

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 states a specific verb and resource — 'Find the exact block number and timestamp at or before an ISO datetime or unix timestamp' — plus explicit scope of 8 named EVM chains. An agent immediately knows this is a time-to-block resolver rather than a raw block fetch. It stops short of naming a sibling (e.g. evm_block) as the contrasting alternative, so it lands at 4 rather than 5.

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?

The two-step x402 protocol is spelled out precisely: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.' That is actionable precondition guidance an agent would otherwise have to guess. There is no guidance on when to prefer this over evm_block or how to choose a chain, so it is clear context without exclusions.

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