Skip to main content
Glama

BRAINIAC Base Chain Data

Search contract event logs

chain-data_logs_search

Search for contract event logs on Base Mainnet with filters for block range, address, and topics. Limited to 1000 results per request. Price $0.05 USDC. POST /api/v1/chain-data/logs/search. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chain-data_logs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
topicsNo
addressNo
toBlockNo
blockHashNo
fromBlockNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the whole behavioral burden and does well: it discloses the 1000-result cap, the $0.05 USDC cost, the POST endpoint, and the exact failure mode (unpaid calls return 402 and do not execute). What it omits is return behavior — ordering of logs, whether results can be paged past the 1000 cap, and response shape.

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?

Five short, front-loaded sentences: purpose first, then constraints, pricing, endpoint, and payment failure. Every sentence is factual and useful, though the 1000-result cap partially restates the schema's maximum/default, which is a small redundancy.

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?

For a 6-parameter, no-annotation, no-output-schema tool, the definition conveys purpose, cost, and payment failure well but leaves real gaps: no block-range defaults or span limits, no explanation of topic-position matching, and no description of what a returned log contains. An agent could call it, but would likely guess on topic semantics and range defaults.

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% across 6 parameters, so the description must compensate and only partly does. It names block range, address, and topics, but says nothing about blockHash, the 1-1000 limit bounds (only implied by the result cap sentence), or the positional semantics of the 4-slot topics array with null wildcards, which is the most error-prone parameter.

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 gives a specific verb and resource ('Search for contract event logs') and pins the network to Base Mainnet, which is critical context absent from the schema. It does not explicitly distinguish itself from adjacent siblings like chain-data_token_erc20-transfers or chain-data_block_transactions, so the agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is implied by naming available filters (block range, address, topics), so an agent can judge this is the right tool for event-log queries. There is no explicit when-to-use versus when-not-to-use guidance, and no statement pointing to alternatives such as token transfer or transaction lookups.

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.

Resources