Skip to main content
Glama

Chainlist

by io.github.pipeworx-io

List Chains

list_chains
Read-onlyIdempotent

Browse or filter the EVM chain registry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCase-insensitive substring filter on chain name
activeNoRestrict to active chains (default true — excludes deprecated)
testnetNoInclude testnets only (true) / mainnets only (false). Default: all.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of chains matching the filter criteria
chainsYesArray of summarized chain objects

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "active": true,
+    "testnet": false
+  },
+  {
+    "active": true,
+    "name": "ethereum"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "chains": {
+      "description": "Array of summarized chain objects",
+      "items": {
+        "properties": {
+          "chainId": {
+            "description": "EVM chain ID",
+            "type": "integer"
+          },
+          "explorers": {
+            "description": "Block explorer URLs",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "description": "Full chain name",
+            "type": "string"
+          },
+          "nativeCurrency": {
+            "description": "Native currency details",
+            "properties": {
+              "decimals": {
+                "description": "Number of decimals",
+                "type": "integer"
+              },
+              "name": {
+                "description": "Currency name",
+                "type": "string"
+              },
+              "symbol": {
+                "description": "Currency symbol",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "rpc_count": {
+            "description": "Number of available RPC endpoints",
+            "type": "integer"
+          },
+          "shortName": {
+            "description": "Short chain identifier (e.g. eth, matic)",
+            "type": "string"
+          },
+          "status": {
+            "description": "Chain status (active, deprecated, incubating)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "chainId",
+          "name",
+          "shortName",
+          "rpc_count",
+          "explorers",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of chains matching the filter criteria",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "count",
+    "chains"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds minimal behavioral context beyond 'browse or filter', which is consistent but doesn't disclose additional traits.

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 sentence that front-loads the purpose and contains no wasted words. It is maximally concise.

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?

Given the low complexity, full annotation coverage, full schema coverage, and presence of an output schema, the description sufficiently informs an agent about the tool's purpose and safe usage.

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%, and the description does not add meaning beyond what the schema already provides for the three parameters. Baseline 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 uses a specific verb ('Browse or filter') and a clear resource ('the EVM chain registry'), clearly distinguishing it from sibling tools like 'get_chain' which targets a single chain.

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

Usage Guidelines3/5

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

The description implies usage for browsing or filtering chains but provides no explicit guidance on when to prefer this tool over alternatives like 'get_chain' or other listing tools.

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

All Chainlist 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.2/5.0
Disambiguation4/5

Tools have distinct purposes with clear descriptions, but ask_pipeworx_beta currently duplicates ask_pipeworx, and the multiple prediction market tools could be confusing without careful reading.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun or noun_verb pattern, with no mixing of conventions.

Tool Count3/5

34 tools is high for a single server, covering chain data, Pipeworx research, and prediction markets. While well-organized, the breadth pushes the boundary of manageable scope.

Completeness4/5

The tool set covers major query operations for chains, entities, and data sources, with subscription and memory features. Minor gaps like lack of chain creation are acceptable given the server's focus on data retrieval.

Resources