Skip to main content
Glama
Sign In
Blockchain MCP Server

Blockchain MCP Server

by lienhage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Function Signatures

4byte

Retrieve Ethereum function signatures using a 4-byte hex selector from the 4byte.directory database. Simplify smart contract interactions by identifying function details quickly and accurately.

Instructions

Get function signatures for the given selector from 4byte.directory

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": {
      "selector": "<selector>"
    },
    "name": "4byte"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesFunction selector (4-byte hex), e.g., '0xa9059cbb' or 'a9059cbb'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't disclose potential behaviors like network calls, rate limits, error handling, or output format. This is a significant gap for a tool with external dependencies.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action, resource, and input, making it highly concise and well-structured.

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 the tool's external dependency (4byte.directory) and lack of annotations or output schema, the description is incomplete. It doesn't explain what a 'function signature' entails, the return format, or error scenarios, leaving gaps in understanding for effective agent use.

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 100%, with the parameter 'selector' fully documented in the schema. The description adds no additional semantic context beyond what the schema provides, such as examples of valid selectors or edge cases. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 clearly states the action ('Get function signatures') and the resource ('from 4byte.directory'), with the specific input ('for the given selector'). It distinguishes from siblings like 'sig' or 'event-sig' by focusing on function signatures from a specific directory. However, it doesn't explicitly differentiate from '4byte-decode' or 'abi-decode', which might have overlapping purposes.

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?

The description provides no guidance on when to use this tool versus alternatives like 'sig', '4byte-decode', or 'abi-decode'. It mentions the source ('4byte.directory') but doesn't specify use cases, prerequisites, or exclusions, leaving the agent to infer usage from context alone.

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

Deploy Server

Other Tools

Related Tools