Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

chain_info

Retrieve chain-specific data for Arbitrum networks including contract addresses, chain IDs, RPC URLs, and native token details to support development and monitoring tasks.

Instructions

Get comprehensive chain information including rollup contract address, bridge addresses, chain ID, RPC URL, explorer URL, native token details, and all bridge contract addresses. Use this for questions about rollup addresses, bridge contracts, chain IDs, or any chain-specific data for Arbitrum chains like Xai, Arbitrum One, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNameYesChain name to look up (e.g., 'Xai', 'Arbitrum One', 'Nova', 'Stylus')

Implementation Reference

  • Executes the chain_info tool by invoking ChainLookupService.findChainByName(chainName) and returning the chain information as JSON text content or error if not found.
    case "chain_info":
      const chainInfo = await this.chainLookupService.findChainByName(
        args.chainName as string
      );
      if (!chainInfo) {
        return {
          content: [
            {
              type: "text",
              text: `Chain "${args.chainName}" not found`,
            },
          ],
        };
      }
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(chainInfo, null, 2),
          },
        ],
      };
  • src/index.ts:1063-1078 (registration)
    Registers the chain_info tool in the list of available tools, including its description and input schema requiring 'chainName'.
    {
      name: "chain_info",
      description:
        "Get comprehensive chain information including rollup contract address, bridge addresses, chain ID, RPC URL, explorer URL, native token details, and all bridge contract addresses. Use this for questions about rollup addresses, bridge contracts, chain IDs, or any chain-specific data for Arbitrum chains like Xai, Arbitrum One, etc.",
      inputSchema: {
        type: "object" as const,
        properties: {
          chainName: {
            type: "string",
            description:
              "Chain name to look up (e.g., 'Xai', 'Arbitrum One', 'Nova', 'Stylus')",
          },
        },
        required: ["chainName"],
      },
    },
  • Defines the OrbitChainData interface which structures the output data returned by the chain_info tool.
    export interface OrbitChainData {
      chainId: number;
      name: string;
      slug: string;
      parentChainId: number;
      rpcUrl: string;
      explorerUrl?: string;
      nativeCurrency: {
        name: string;
        symbol: string;
        decimals: number;
      };
      isArbitrum: boolean;
      isMainnet: boolean;
      isCustom?: boolean;
      isTestnet?: boolean;
      
      // Ethereum Bridge Contract Addresses (nested under ethBridge)
      ethBridge?: {
        bridge: string;
        inbox: string;
        outbox: string;
        rollup: string;
        sequencerInbox: string;
      };
      
      // Legacy flat structure for backward compatibility
      bridge?: string;
      inbox?: string;
      outbox?: string;
      rollup?: string;
      sequencerInbox?: string;
      
      // Token Bridge Contract Addresses
      parentCustomGateway?: string;
      parentErc20Gateway?: string;
      parentGatewayRouter?: string;
      childCustomGateway?: string;
      childErc20Gateway?: string;
      childGatewayRouter?: string;
      
      // UI Configuration
      color?: string;
      description?: string;
      logo?: string;
      
      // Native Token (for custom tokens)
      nativeToken?: {
        name: string;
        symbol: string;
        decimals: number;
        address?: string;
      };
    }
  • Core helper function that performs fuzzy matching on chain names (exact, slug, partial) to retrieve OrbitChainData from cached chains list.
    async findChainByName(name: string): Promise<OrbitChainData | null> {
      await this.ensureChainsData();
      
      const searchName = name.toLowerCase().trim();
      
      // Try exact name match first
      let chain = this.chainsData.find(chain => 
        chain.name.toLowerCase() === searchName
      );
      
      if (!chain) {
        // Try slug match
        chain = this.chainsData.find(chain => 
          chain.slug?.toLowerCase() === searchName
        );
      }
      
      if (!chain) {
        // Try partial name match
        chain = this.chainsData.find(chain => 
          chain.name.toLowerCase().includes(searchName) ||
          searchName.includes(chain.name.toLowerCase())
        );
      }
      
      return chain || null;
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes what data is returned (comprehensive chain information) but lacks details on behavioral traits such as error handling (e.g., what happens if chainName is invalid), performance characteristics (e.g., response time), or data freshness. The description is accurate but minimal on behavioral aspects beyond the core functionality.

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 efficiently structured in two sentences: the first lists all returned data comprehensively, and the second provides usage guidelines with examples. Every sentence adds value without redundancy, making it easy for an agent to parse and apply.

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?

Given the tool's complexity (single parameter, no output schema, no annotations), the description is mostly complete. It clearly states the purpose, usage, and data returned. However, it lacks details on output format (e.g., JSON structure) and error handling, which could be important for an agent to interpret results correctly. The absence of an output schema means the description should ideally cover return values more explicitly.

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 description coverage is 100%, so the schema already documents the 'chainName' parameter with examples. The description adds value by specifying the scope ('Arbitrum chains like Xai, Arbitrum One, etc.') and implying that valid chain names are needed, but it doesn't provide additional syntax or format details beyond what the schema offers. With 0 parameters beyond the documented one, a baseline of 4 is appropriate as the description compensates slightly for the lack of output schema.

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 specific action ('Get comprehensive chain information') and enumerates the exact resources returned (rollup contract address, bridge addresses, chain ID, RPC URL, explorer URL, native token details, bridge contract addresses). It distinguishes itself from siblings like 'get_rollup_address' or 'list_chains' by emphasizing comprehensive data retrieval rather than single attributes or listings.

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 states when to use this tool: 'for questions about rollup addresses, bridge contracts, chain IDs, or any chain-specific data for Arbitrum chains like Xai, Arbitrum One, etc.' It provides clear context and examples of appropriate use cases, helping the agent differentiate from alternatives like 'get_rollup_address' (which only gets one address) or 'list_chains' (which lists chains without detailed info).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dewanshparashar/arbitrum-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server