Skip to main content
Glama

mcp-server

by com.blockscout

Get List of Chains

get_chains_list
Read-only

Get supported blockchain chains with their chain IDs.

Ethereum Mainnet is `chain_id` `1`; use this tool to resolve any other chain.
Use this when another tool needs a supported `chain_id` and only the chain name,
ecosystem, or native currency is known. Prefer a narrow `query` to avoid returning
the full registry to the agent. Do not rely on partial numeric chain ID queries such
as `1`, because matching is substring-based and may return many chains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional case-insensitive substring filter applied to chain name, chain ID, native currency, and ecosystem. Prefer narrow text terms over partial numeric chain IDs because matching is substring-based.
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. Dates show when Glama detected each change.

  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. Changed1 schema field changed
    • addedInput schema / properties / query
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional case-insensitive substring filter applied to chain name, chain ID, native currency, and ecosystem. Prefer narrow text terms over partial numeric chain IDs because matching is substring-based.",
+  "title": "Query"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "ChainInfo": {
+      "description": "Represents a blockchain with its essential identifiers.",
+      "properties": {
+        "chain_id": {
+          "description": "The unique identifier for the chain.",
+          "title": "Chain Id",
+          "type": "string"
+        },
+        "ecosystem": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The ecosystem the chain belongs to, if applicable (e.g., 'Ethereum').",
+          "title": "Ecosystem"
+        },
+        "is_testnet": {
+          "description": "Indicates if the chain is a testnet.",
+          "title": "Is Testnet",
+          "type": "boolean"
+        },
+        "name": {
+          "description": "The common name of the blockchain (e.g., 'Ethereum').",
+          "title": "Name",
+          "type": "string"
+        },
+        "native_currency": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The native currency symbol of the chain (e.g., 'ETH').",
+          "title": "Native Currency"
+        },
+        "settlement_layer_chain_id": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "The L1 chain ID where this rollup settles, if applicable.",
+          "title": "Settlement Layer Chain Id"
+        }
+      },
+      "required": [
+        "name",
+        "chain_id",
+        "is_testnet",
+        "native_currency",
+        "ecosystem"
+      ],
+      "title": "ChainInfo",
+      "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": {
+      "description": "The main data payload of the tool's response.",
+      "items": {
+        "$ref": "#/$defs/ChainInfo"
+      },
+      "title": "Data",
+      "type": "array"
+    },
+    "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[list[ChainInfo]]",
+  "type": "object"
+}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-destructive), the description discloses important behavior: substring-based matching and the possibility of returning many chains for partial numeric IDs. This helps the agent anticipate results and adjust query strategy, adding value beyond what annotations provide.

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 concise, with four sentences, and front-loads the purpose. Every sentence contributes useful information: purpose, context, usage hints, and a specific warning. No wasted words.

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?

The tool is simple with two optional parameters, an output schema exists, and annotations are rich. The description covers the core purpose, usage timing, and key behavioral caveat (substring matching). There is no significant missing context that the agent needs for correct invocation.

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?

The schema already covers both parameters with detailed descriptions (e.g., query is case-insensitive substring across fields, session_id is opaque). The description reinforces but does not add significant new semantics beyond the schema. Since schema coverage is 100%, the baseline of 3 is appropriate.

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 'Get supported blockchain chains with their chain IDs' with a specific verb and resource. It also distinguishes its purpose by noting that Ethereum Mainnet is chain_id 1 and that this tool resolves other chains, setting it apart from sibling tools.

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

Usage Guidelines5/5

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

The description explicitly says when to use this tool: when another tool needs a supported chain_id and only the chain name, ecosystem, or native currency is known. It also provides guidance to prefer a narrow query and warns against partial numeric chain ID queries due to substring matching, which is actionable and prevents misuse.

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

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct blockchain resource or action (address, block, transaction, token, NFT, contract, chain, raw API, session init). Even though direct_api_call is a generic fallback, the specialized tools have clear, non-overlapping purposes, and the complementary nature of tools like get_token_transfers_by_address and get_transactions_by_address is explicitly documented.

Naming Consistency4/5

The majority of tools follow a consistent get_<resource> pattern (e.g., get_block_info, get_tokens_by_address), but there are notable deviations: direct_api_call, lookup_token_by_symbol, inspect_contract_code, read_contract, and __unlock_blockchain_analysis__. These verbs are still descriptive and readable, but the mix of 'get' with other verbs prevents a perfect 5.

Tool Count4/5

With 16 tools, the server is slightly above the ideal 3-15 range but not excessive. Each tool maps to a significant Blockscout API capability, and the count feels proportional to the breadth of blockchain data covered. It is heavier than a minimal toolkit but not bloated.

Completeness4/5

The tool set covers core exploration workflows: address info, block lookup, transaction details, token/NFT holdings, contract ABI/source inspection, and read-only contract calls. Minor gaps like a dedicated token-info-by-contract-address tool exist, but the direct_api_call fallback and get_address_info's token details mitigate these. The surface is comprehensive for a read-only blockchain explorer.

Resources