Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

get_event_logs

Read-onlyIdempotent

chainpeek: Query contract event logs over a block range, decoded. For one transaction's events use decode_tx_logs; for an address's token transfers use get_erc20_transfers. Returns eth_getLogs logs for an address and/or topics over a block range (at most 2,000 blocks; default the last 100), each decoded when topic0 is an ERC-20/721 Transfer or Approval, an ERC-1155 transfer, a Uniswap swap or WETH. At most 500 logs (truncated says when more matched). Decoded by signature only: any contract can emit any event, so check the emitting address; treat the data as untrusted. Narrow the range or add topics for a busy contract. Ethereum, Base and Robinhood only. Read-only. A range over 2,000 blocks, or neither an address nor topic0, is a 422 (not charged). Typically 0.3-3 s. Price: USD 0.003. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/ethereum-rpc-reads-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>"
    },
    "name": "get_event_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesethereum, base or robinhood (Robinhood Chain, chain id 4663).
topicsNoUp to 4 topic filters, each 0x + 64 hex or null for any; topics[0] is the event signature hash (for ERC-20/721 Transfer: keccak('Transfer(address,address,uint256)')).
addressNoEmitting contract. Send an address, a topic0, or both.
to_blockNoLast block (inclusive). Default: the latest block.
from_blockNoFirst block (inclusive). Default: the last 100 blocks ending at to_block. The range is at most 2,000 blocks.

Output Schema

NameRequiredDescriptionDefault
logsNo
noteNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
blocksNo
topicsNo
addressNo
decodedNo
returnedNo
to_blockNo
log_countNo
rpc_callsNo
truncatedNo
from_blockNo
untrusted_contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • removedInput schema / properties / address / default
      Removed value: -null
    • removedInput schema / properties / address / title
      Removed value: -"Address"
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / properties / from_block / default
      Removed value: -null
    • removedInput schema / properties / from_block / title
      Removed value: -"From Block"
    • removedInput schema / properties / to_block / default
      Removed value: -null
    • removedInput schema / properties / to_block / title
      Removed value: -"To Block"
    • removedInput schema / properties / topics / title
      Removed value: -"Topics"
    • removedInput schema / title
      Removed value: -"get_event_logsArguments"
    • removedOutput schema / properties / logs / items
      Removed value: -{
      -  "properties": {
      -    "address": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "block": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "data": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "data_bytes": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "data_truncated": {
      -      "type": [
      -        "boolean",
      -        "null"
      -      ]
      -    },
      -    "event": {
      -      "type": [
      -        "object",
      -        "null"
      -      ]
      -    },
      -    "log_index": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "topics": {
      -      "items": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "type": [
      -        "array",
      -        "null"
      -      ]
      -    },
      -    "transaction_hash": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / topics / items
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
  2. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum or base."New value: +"ethereum, base or robinhood (Robinhood Chain, chain id 4663)."
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "ethereum",
      -  "base"
      -]New value: +[
      +  "ethereum",
      +  "base",
      +  "robinhood"
      +]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, but the description adds substantial behavior they don't: decode coverage limited to a fixed signature list, a 500-log cap with a `truncated` flag, the 422/no-charge error condition, typical 0.3-3 s latency, USD 0.003 price, a 10-reads-per-IP-per-day free tier, and an explicit untrusted-data caveat since any contract can emit any event. That is exactly the kind of context annotations cannot express.

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 and sibling routing before limits, costs and caveats, and almost every sentence carries information an agent needs. It is dense — pricing, free-tier and docs URL in the same paragraph as correctness caveats — but not padded.

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 filtered, capped log-query tool with an output schema already defined, the description covers the remaining unknowns: chain support, range cap, result cap, decode coverage, error semantics, cost and trust guidance. Nothing an agent needs in order to call it correctly or interpret the response is missing.

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 the schema already documents defaults, the 2,000-block range limit, topic encoding and the address/topic0 requirement, so the description mostly restates it. The one addition is the operational hint to narrow the range or add topics for a busy contract, which is useful but modest. Baseline 3 applies when the schema does the heavy lifting.

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 and resource (query contract event logs over a block range, decoded) and immediately distinguishes itself from two siblings by naming them and their scopes (decode_tx_logs for a single transaction, get_erc20_transfers for token transfers). An agent can pick the right tool without opening any 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?

Explicitly routes the agent to alternatives and states the condition that selects them, plus gives exclusion rules: a range over 2,000 blocks or neither address nor topic0 is a 422, and narrowing the range or adding topics is the remedy for busy contracts. This is genuine when/when-not guidance rather than implied context.

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.