Skip to main content
Glama

Chainlist

by io.github.pipeworx-io

Get Chain

get_chain
Read-onlyIdempotent

Fetch a single chain by chainId (number) or shortName (e.g. "eth", "matic", "arb1").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chain_id_or_short_nameYesChain id as string or shortName

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rpcNoRPC endpoint URLs
nameYesChain name
chainYesChain identifier
statusNoChain status (active, deprecated, incubating)
chainIdYesEVM chain ID
faucetsNoFaucet URLs for testnet tokens
infoURLNoChain information URL (optional)
explorersNoBlock explorers
networkIdNoNetwork ID (optional)
shortNameYesShort chain name
nativeCurrencyNoNative currency details

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: +[
+  {
+    "chain_id_or_short_name": "eth"
+  },
+  {
+    "chain_id_or_short_name": "1"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "chain": {
+      "description": "Chain identifier",
+      "type": "string"
+    },
+    "chainId": {
+      "description": "EVM chain ID",
+      "type": "integer"
+    },
+    "explorers": {
+      "description": "Block explorers",
+      "items": {
+        "properties": {
+          "name": {
+            "description": "Explorer name",
+            "type": "string"
+          },
+          "standard": {
+            "description": "Standard type (optional)",
+            "type": "string"
+          },
+          "url": {
+            "description": "Explorer URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "faucets": {
+      "description": "Faucet URLs for testnet tokens",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "infoURL": {
+      "description": "Chain information URL (optional)",
+      "type": "string"
+    },
+    "name": {
+      "description": "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"
+    },
+    "networkId": {
+      "description": "Network ID (optional)",
+      "type": "integer"
+    },
+    "rpc": {
+      "description": "RPC endpoint URLs",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "shortName": {
+      "description": "Short chain name",
+      "type": "string"
+    },
+    "status": {
+      "description": "Chain status (active, deprecated, incubating)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "chain",
+    "shortName",
+    "chainId"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds that it fetches a single chain, which is consistent. No behavioral traits beyond annotations are missing.

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?

Single sentence, no wasted words, front-loaded with purpose and parameter details. Highly concise.

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

Completeness4/5

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

For a simple fetch tool with 1 param and output schema, the description covers essential purpose. Missing note about not-found behavior, but overall adequate.

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?

Schema coverage is 100%, but description adds value by explaining parameter can be number string or shortName, with concrete examples. Adds clarity beyond schema description.

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?

Clearly states verb 'Fetch', resource 'single chain', and identification method via chainId or shortName with examples. Distinguishes from sibling 'list_chains' and 'find_rpc'.

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?

Implied usage: use when you have a chain identifier and want a single chain. No explicit when-not or alternatives mentioned, but context with sibling tools provides implicit distinction.

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