lookup_selectorLookup gulltoppr-proven signatures for a 4-byte function/error selector or 32-byte event topic0. Prefer these over public 4byte guesses.
| Name | Required | Description | Default |
|---|---|---|---|
| selector | Yes | 4-byte function/error selector or 32-byte event topic0. |
| Name | Required | Description | Default |
|---|---|---|---|
| entries | Yes | ||
| selector | Yes | 4-byte function/error selector or 32-byte event topic0. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe read operation with possible missing results. The description adds that signatures are 'gulltoppr-proven,' hinting at data source quality, but does not significantly expand on behavioral traits beyond what annotations convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise: two sentences, no wasted words. The core purpose is front-loaded in the first sentence, and the second sentence adds a valuable usage hint. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (single parameter, clear schema, annotations, and output schema), the description is complete. It adequately explains the tool's purpose and provides a usage preference, leaving no critical gaps for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers the single parameter with 100% coverage, including a regex pattern and description. The description merely restates the parameter's purpose ('4-byte function/error selector or 32-byte event topic0'), adding no new semantic information beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Lookup gulltoppr-proven signatures for a 4-byte function/error selector or 32-byte event topic0.' It uses a specific verb (lookup) and resource (signatures), and distinguishes from siblings like decode_tx or resolve_abi by focusing on selector-based lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The instruction 'Prefer these over public 4byte guesses' provides clear guidance on when to use this tool, implying it should be chosen over less reliable alternatives. However, it does not explicitly state when not to use it or mention any other alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: decode vs encode, prepare vs simulate, resolve ABI vs selector, etc. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., decode_tx, list_chains, resolve_abi, runtime_metrics). The only exception is 'simulate', which is a single verb but still clear and consistent with the style.
12 tools is an ideal count for a blockchain interaction server. Each tool covers a necessary step in the workflow without being overwhelming or sparse.
The tool set covers the full lifecycle of contract interaction: resolve ABI, encode/decode, simulate, prepare unsigned transactions, look up selectors, resolve names, and list chains. No obvious gaps given the server's purpose of preparing actions for external signing.