Crypto, web, finance and app data tools

Contract Event Logs

event_logs

Event logs a contract emitted (eth_getLogs), filtered by event signature such as Transfer(address,address,uint256) or a topic hash, over a block range (max 5,000 blocks, default last 100). Use to monitor swaps, mints or governance.

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

Input Schema

Name	Required	Default
`chain`	No	ethereum
`event`	No
`limit`	No
`address`	Yes
`to_block`	No
`from_block`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the block range limit (max 5,000 blocks) and default (last 100), which is useful. But it does not explicitly state that this is a read-only operation, nor does it mention rate limits, authentication, or the meaning of the limit parameter. Eth_getLogs implies read-only, but the disclosure is incomplete for a tool without annotations.

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?

The description is a single, front-loaded sentence that efficiently packs the purpose, method, filters, constraints, and usage examples. It is appropriately sized with little waste, though it could be slightly more structured for readability.

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

Completeness3/5

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

Given six parameters, no annotations, and an output schema, the description covers the main use case and block range constraints. But it leaves several parameters (chain, limit, address) and behavioral details (read-only nature, rate limits) unaddressed. It is adequate but not complete for a tool of this complexity.

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 description coverage is 0%, so the description needs to compensate. It explains the event signature format and block range constraints for from_block/to_block, which are the trickiest parameters. However, it leaves chain, limit, and address undefined, and the limit parameter (default 100) is not clarified. Partial compensation justifies a 3.

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: 'Event logs a contract emitted (eth_getLogs)'. It uses the method name and examples to distinguish itself from generic contract reads or token transfers, though it never explicitly names a sibling tool. The filtering over event signatures and block ranges makes the purpose clear enough to select it over similar tools.

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?

It gives a clear usage context: 'Use to monitor swaps, mints or governance.' This tells the agent when to reach for this tool. However, it does not explicitly list alternatives or when NOT to use it (e.g., versus erc20_transfers for standard token transfers), leaving a small gap.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?