Skip to main content
Glama
dewanshparashar

Arbitrum MCP Server

list_chains

Discover available Arbitrum Orbit chains by retrieving their names for querying and monitoring purposes.

Instructions

List all available Arbitrum Orbit chains and their names. Use this to see what chains are available for querying.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'list_chains' MCP tool. Calls ChainLookupService.listChainNames() and returns a formatted text response listing all available chain names.
    case "list_chains":
      const chainNames = await this.chainLookupService.listChainNames();
      return {
        content: [
          {
            type: "text",
            text: `Available chains:\n${chainNames.join("\n")}`,
          },
        ],
      };
  • src/index.ts:1038-1046 (registration)
    Tool registration in getAvailableTools(). Defines the 'list_chains' tool name, description, and empty input schema (no parameters required). Returned by ListToolsRequestSchema handler.
    {
      name: "list_chains",
      description:
        "List all available Arbitrum Orbit chains and their names. Use this to see what chains are available for querying.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
    },
  • Input schema definition for 'list_chains' tool: empty object (no input parameters). Part of the tool registration object.
    inputSchema: {
      type: "object" as const,
      properties: {},
    },
  • Helper method in ChainLookupService that retrieves and sorts the list of all known chain names. Called by the 'list_chains' handler.
    async listChainNames(): Promise<string[]> {
      await this.ensureChainsData();
      return this.chainsData.map(chain => chain.name).sort();
    }
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 mentions 'list all available' but lacks details on pagination, rate limits, or response format. However, it does imply a read-only operation and hints at use for querying preparation, adding some behavioral context beyond the basic purpose.

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 two concise sentences with zero waste: the first states the purpose, and the second provides usage guidance. It's front-loaded with the core function and efficiently communicates essential information without redundancy.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is adequate but could be more complete. It covers purpose and usage well, but lacks details on output format or behavioral traits like performance. For a list tool, this is minimal but viable, leaving some gaps in full context.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, but that's unnecessary here. A baseline of 4 is appropriate as it compensates for the lack of parameters by clearly stating the tool's scope.

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 verb 'list' and the resource 'Arbitrum Orbit chains and their names', making the purpose specific and unambiguous. It distinguishes from siblings like 'search_chains' by emphasizing 'all available' without filtering, and from 'chain_info' which likely provides details on a specific chain rather than listing them.

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 'Use this to see what chains are available for querying', providing clear context for when to use this tool. It differentiates from 'search_chains' by implying this lists all chains without search criteria, and from query-focused siblings like 'arbtrace_call' by indicating it's for discovery before querying.

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