Skip to main content
Glama
lienhage

Blockchain MCP Server

by lienhage

event-sig

event-sig

Extract event selectors for Ethereum smart contracts by inputting event names. Use this tool to simplify interactions with blockchain events and enhance contract analysis.

Instructions

get event selector

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventNameYesevent name, e.g. 'Transfer(address indexed from, address indexed to, uint256 amount)'

Implementation Reference

  • The handler function for the "event-sig" tool. It computes the event selector by hashing the event name with keccak256 and taking the first 10 characters (4 bytes).
    async ({ eventName }) => {
        const eventSignature = ethers.keccak256(ethers.toUtf8Bytes(eventName)).slice(0, 10);
        return {
        content: [{ type: "text", text: `event signature: ${eventSignature}` }]
        };
    }
  • Schema definition including title, description, and input schema using Zod for the eventName parameter.
    {
      title: "event-sig",
      description: "get event selector",
      inputSchema: {
          eventName: z.string().describe("event name, e.g. 'Transfer(address indexed from, address indexed to, uint256 amount)'"), 
      }
    },
  • Registration of the "event-sig" tool within the UtilsService.registerWithServer method using server.registerTool.
    // register tools to get event signature
    server.registerTool(
      "event-sig",
      {
        title: "event-sig",
        description: "get event selector",
        inputSchema: {
            eventName: z.string().describe("event name, e.g. 'Transfer(address indexed from, address indexed to, uint256 amount)'"), 
        }
      },
        async ({ eventName }) => {
            const eventSignature = ethers.keccak256(ethers.toUtf8Bytes(eventName)).slice(0, 10);
            return {
            content: [{ type: "text", text: `event signature: ${eventSignature}` }]
            };
        }
    );
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is read-only, has side effects, requires authentication, or handles errors, which is insufficient for a tool with no annotation coverage.

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

Conciseness5/5

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

The description is extremely concise with three words, front-loaded and zero waste. Every word earns its place, making it efficient in structure.

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?

Given no annotations, no output schema, and a single parameter, the description is incomplete. It lacks context on what an event selector is, how it's used, or what the tool returns, leaving significant gaps for the agent.

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 coverage is 100%, with the parameter 'eventName' well-described in the schema. The description adds no additional meaning beyond the schema, so it meets the baseline for high schema coverage without compensating value.

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?

The description 'get event selector' states a verb ('get') and resource ('event selector'), but is vague about what an 'event selector' is or its purpose. It doesn't distinguish from siblings like 'sig' or 'abi-encode-with-signature', leaving ambiguity in scope.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lienhage/blockchain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server