Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

get_block_at_time

Read-onlyIdempotent

chainpeek: find the block at a point in time on Ethereum, Base or Robinhood Chain. For the latest block use get_block_number. Returns block (the last block at or before the time) and next_block, or is_latest: true when the time is at or after the head. A time before Base's genesis is a 422 before_genesis (not charged). A malformed or inconsistent node answer is a 5xx and is not charged. Typically 1-3 s (about 3-6 reads). Price: USD 0.003. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/block-at-timestamp-api.html

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>",
      "timestamp": "<timestamp>"
    },
    "name": "get_block_at_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain to read.
timestampYesUnix seconds or ISO 8601 (no offset = UTC), e.g. 2026-01-01T00:00:00Z.

Output Schema

NameRequiredDescriptionDefault
blockNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
is_latestNo
rpc_callsNo
timestampNo
next_blockNo
assumed_utcNo
timestamp_isoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / properties / timestamp / title
      Removed value: -"Timestamp"
    • removedInput schema / title
      Removed value: -"get_block_at_timeArguments"
    • removedOutput schema / properties / block / properties
      Removed value: -{
      -  "number": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "timestamp": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "timestamp_iso": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
    • removedOutput schema / properties / next_block / properties
      Removed value: -{
      -  "number": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "timestamp": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "timestamp_iso": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "ethereum",
      -  "base"
      -]New value: +[
      +  "ethereum",
      +  "base",
      +  "robinhood"
      +]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "assumed_utc": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "block": {
      +      "properties": {
      +        "number": {
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "timestamp": {
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "timestamp_iso": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "chain": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "is_latest": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "next_block": {
      +      "properties": {
      +        "number": {
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "timestamp": {
      +          "type": [
      +            "integer",
      +            "null"
      +          ]
      +        },
      +        "timestamp_iso": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "rpc_calls": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "timestamp": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "timestamp_iso": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, but the description adds return-shape semantics (block, next_block, is_latest), two distinct failure modes with billing consequences (422 before_genesis not charged, 5xx not charged), typical latency of 1-3 s, price, and the free-tier quota. That is substantial context beyond structured fields.

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?

Front-loaded with purpose, then the sibling pointer, then return shape and error semantics – good ordering with no filler. It is a dense run-on of short clauses and includes pricing/docs detail that is useful but sits at a lower priority than the call semantics.

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 two-required-param read tool with an output schema, the description covers everything an agent needs: which chain values work, what comes back, how failures are signaled and billed, latency, and cost. Nothing material is left to guesswork.

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% and both parameters are documented with an enum and an ISO/Unix example, so the baseline is 3. The description only implicitly touches parameter meaning ('a time before Base's genesis', listing supported chains) and adds no format or precedence guidance 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?

States a specific verb ('find the block') plus resource ('at a point in time') and scope (Ethereum, Base, Robinhood Chain), and explicitly distinguishes itself from get_block_number for the latest-block case. An agent can select it without opening the schema.

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?

Names the alternative ('For the latest block use get_block_number') with the exact condition that selects it, and adds an edge-case rule for times before Base's genesis. Use/when-not-to-use is explicit rather than inferred.

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.