Vitruveo Chain Tools MCP

contract logs

contract_logs

Read-only

Reads contract event logs within a bounded block range and record limit, returning explicit completeness details so you can verify whether all matching logs were retrieved.

Instructions

Read at most 2000 blocks and 500 log records; explicit completeness.

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": {
      "address": "<address>",
      "fromBlock": "<fromBlock>",
      "toBlock": "<toBlock>"
    },
    "name": "contract_logs"
  }
}

Input Schema

Name	Required	Description	Default
`topic`	No
`address`	Yes
`toBlock`	Yes
`fromBlock`	Yes
`maxRecords`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0-rc.1Nov 9, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already cover safety (readOnlyHint true, destructiveHint false, openWorldHint true), so the description's real contribution is the hard caps of 2000 blocks and 500 records, which are not in the structured data. However, "explicit completeness" is cryptic — it hints that truncation is surfaced rather than silent, but never says so plainly, and it says nothing about pagination or error behavior on oversized ranges.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact clause with no filler, but the phrase "explicit completeness" is opaque jargon that costs a sentence slot without conveying a concrete behavior. The limits are front-loaded, which is good, but the fragment lacks a subject.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five parameters at 0% schema coverage with no output schema leaves the agent guessing about topic semantics, block number format, and what the returned records look like. The one genuinely useful fact (caps) is present, but the definition is under-specified for a tool with this many undocumented inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, yet it only implies the block-range cap and record cap. It never explains that topic is a 32-byte event signature/topic hash, that fromBlock/toBlock accept decimal strings or "latest", or why address is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read ... log records" does give a verb and resource, but the sentence leads with limits rather than stating that it fetches event logs for a contract address over a block range. It never distinguishes itself from the sibling decode_event_logs, so an agent cannot tell which one to pick from the description alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative. The nearest siblings (decode_event_logs, address_history_page, contract_inspect) are never referenced, leaving the agent to infer selection criteria.

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

Deploy Server