Skip to main content
Glama

blockscout-mcp-server

by ai.smithery
OverviewDiscussionsAdmin

Get Address by ENS Name

get_address_by_ens_name
Read-only

Useful for when you need to convert an ENS domain name (e.g. "blockscout.eth") to its corresponding Ethereum address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesENS domain name to resolve
session_idNoOpaque session identifier.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe main data payload of the tool's response.
notesNoA list of important contextual notes, such as warnings about data truncation or data quality issues.
paginationNoPagination information, present only if the 'data' is a single page of a larger result set.
content_textNoOptional human-readable summary used for MCP content responses.
instructionsNoA list of suggested follow-up actions or instructions for the LLM to plan its next steps.
data_descriptionNoA list of notes explaining the structure, fields, or conventions of the 'data' payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / session_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Opaque session identifier.",
+  "title": "Session Id"
+}
  2. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / name / title
      Added value: +"Name"
    • addedInput schema / title
      Added value: +"get_address_by_ens_nameArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "EnsAddressData": {
+      "description": "A structured representation of an ENS name resolution.",
+      "properties": {
+        "resolved_address": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "The resolved Ethereum address corresponding to the ENS name, or null if not found.",
+          "title": "Resolved Address"
+        }
+      },
+      "title": "EnsAddressData",
+      "type": "object"
+    },
+    "NextCallInfo": {
+      "description": "A structured representation of the tool call required to get the next page.",
+      "properties": {
+        "params": {
+          "additionalProperties": true,
+          "description": "A complete dictionary of parameters for the next tool call, including the new cursor.",
+          "title": "Params",
+          "type": "object"
+        },
+        "tool_name": {
+          "description": "The name of the tool to call for the next page.",
+          "title": "Tool Name",
+          "type": "string"
+        }
+      },
+      "required": [
+        "tool_name",
+        "params"
+      ],
+      "title": "NextCallInfo",
+      "type": "object"
+    },
+    "PaginationInfo": {
+      "description": "Contains the structured information needed to retrieve the next page of results.",
+      "properties": {
+        "next_call": {
+          "$ref": "#/$defs/NextCallInfo",
+          "description": "The structured tool call required to fetch the subsequent page."
+        }
+      },
+      "required": [
+        "next_call"
+      ],
+      "title": "PaginationInfo",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "content_text": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Optional human-readable summary used for MCP content responses.",
+      "title": "Content Text"
+    },
+    "data": {
+      "$ref": "#/$defs/EnsAddressData",
+      "description": "The main data payload of the tool's response."
+    },
+    "data_description": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "A list of notes explaining the structure, fields, or conventions of the 'data' payload.",
+      "title": "Data Description"
+    },
+    "instructions": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "A list of suggested follow-up actions or instructions for the LLM to plan its next steps.",
+      "title": "Instructions"
+    },
+    "notes": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "A list of important contextual notes, such as warnings about data truncation or data quality issues.",
+      "title": "Notes"
+    },
+    "pagination": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/PaginationInfo"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Pagination information, present only if the 'data' is a single page of a larger result set."
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "title": "ToolResponse[EnsAddressData]",
+  "type": "object"
+}
  3. Changed4 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / name / title
      Removed value: -"Name"
    • removedInput schema / title
      Removed value: -"get_address_by_ens_nameArguments"
  4. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read. The description adds that it 'convert's an ENS name, but does not disclose additional behavioral details such as error handling for invalid names or reliance on external data. Given the annotation coverage, a score of 3 is appropriate.

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, focused sentence that immediately conveys the tool's purpose with no extraneous content. It is front-loaded and well-structured.

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

Completeness5/5

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

For a simple lookup tool with full schema coverage, clear annotations, and an output schema, the description is complete. It does not need to explain return values because the output schema exists, and the one-sentence description adequately covers the tool's function.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes both parameters with 100% coverage, so the baseline is 3. The description provides a concrete example 'blockscout.eth' which clarifies the expected format of the 'name' parameter, adding value beyond the schema. No additional information is given for session_id, but it is a generic opaque identifier.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool converts an ENS domain name to its corresponding Ethereum address, using a specific verb and resource. The example 'blockscout.eth' adds concrete context, and it is distinct from sibling tools which focus on blocks, transactions, or tokens.

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?

The description says 'Useful for when you need to convert an ENS domain name' which clearly indicates the appropriate context. It does not explicitly mention alternatives or exclusions, but no other sibling tool serves this purpose, so the guidance is sufficient.

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

All blockscout-mcp-server toolsInspect
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