Tanod MCP server

chainpeek: contract event logs over a block range (eth_getLogs) on Ethereum, Base or Robinhood Chain

get_event_logs

Read-onlyIdempotent

Query decoded contract event logs over a block range for an address or topics. Returns eth_getLogs with up to 500 logs, decoding ERC-20/721/1155 transfers and Uniswap swaps.

Instructions

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 into an event 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

Input Schema

TableJSON Schema

Name	Required	Description
`chain`	Yes	ethereum, base or robinhood (Robinhood Chain, chain id 4663).
`topics`	No	Up 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)')).
`address`	No	Emitting contract. Send an address, a topic0, or both.
`to_block`	No	Last block (inclusive). Default: the latest block.
`from_block`	No	First block (inclusive). Default: the last 100 blocks ending at to_block. The range is at most 2,000 blocks.

Output Schema

TableJSON Schema

Name	Required	Description
`logs`	No
`note`	No
`chain`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`blocks`	No
`topics`	No
`address`	No
`decoded`	No
`returned`	No
`to_block`	No
`log_count`	No
`rpc_calls`	No
`truncated`	No
`from_block`	No
`untrusted_content`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/openWorld) with constraints and traits the agent can't get elsewhere: 2,000-block cap, default last 100 blocks, 500-log truncation with a `truncated` flag, decode-by-signature caveat that data is untrusted, the 422 error path (not charged), latency 0.3-3 s, price, and free-tier quota.

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-loads purpose, then alternatives, then constraints and operational facts in a logical order. It is dense and slightly long, with some redundancy against the title, but nearly every clause carries actionable information.

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 5-param filtered-log tool with an output schema and full annotation coverage, the description supplies everything an agent needs: scope, alternatives, limits, error behavior, and the untrusted-data caveat. Returned values are covered by the output schema, so no gap remains.

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 adds useful framing by tying topics[0] to the event-signature concept and clarifying the address/topic0 requirement to narrow a busy contract. It doesn't restate every field's syntax, but the added decode semantics exceed the schema baseline.

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+resource+scope ('Query contract event logs over a block range, decoded') and immediately distinguishes itself from siblings by name ('For one transaction's events use decode_tx_logs; for an address's token transfers use get_erc20_transfers'). An agent can select it 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 names the two closest alternatives and the condition that routes to each, and adds practical guidance ('Narrow the range or add topics for a busy contract') plus a when-not rule ('A range over 2,000 blocks, or neither an address nor topic0, is a 422'). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server