Skip to main content
Glama

getSupportedNetworks

Retrieve a list of all supported blockchain networks and their configurations for interacting with Ethereum-based systems through the MCP Ethers Wallet server.

Instructions

Get a list of all supported networks and their configurations. For more detailed information about networks, use the getAllNetworks and getNetwork tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The complete registration and inline handler for the 'getSupportedNetworks' tool. It takes no parameters, calls ethersService.getSupportedNetworks(), and returns the networks as formatted JSON or an error message.
    server.tool(
      "getSupportedNetworks",
      "Get a list of all supported networks and their configurations. For more detailed information about networks, use the getAllNetworks and getNetwork tools.",
      {},
      async () => {
        try {
          const networks = await ethersService.getSupportedNetworks();
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify(networks, null, 2)
            }]
          };
        } catch (error) {
          return {
            isError: true,
            content: [{ 
              type: "text", 
              text: `Error getting supported networks: ${error instanceof Error ? error.message : String(error)}`
            }]
          };
        }
      }
    );
  • Calls registerCoreTools which registers the getSupportedNetworks tool among others.
    registerCoreTools(server, ethersService);
  • src/mcpServer.ts:51-51 (registration)
    Top-level registration call that leads to getSupportedNetworks tool being registered.
    registerAllTools(server, ethersService);
  • Defines the list of DEFAULT_PROVIDERS which is likely returned by ethersService.getSupportedNetworks().
    export const DEFAULT_PROVIDERS: DefaultProvider[] = [
      "Ethereum",
      "Polygon PoS",
      "Arbitrum",
      "Arbitrum Nova",
      "Optimism",
      "Avalanche C-Chain",
      "Gnosis",
      "CrossFi",
      "Berachain",
      "Lens",
      "World Chain",
      "Base",
      "Unichain",
      "Geist",
      "ZKsync",
      "Abstract",
      "Polygon zkEVM",
      "Blast",
      "Linea",
      "Flow",
      "Soneium",
      "Fantom Opera",
      "BNB Smart Chain",
      "opBNB Chain",
      "Rootstock",
      "Lumia",
      "ZetaChain",
      "Mantle",
      "Metis",
      "Astar",
      "Holešky",
      "Scroll",
      "Monad Testnet",
      "MEGA Testnet",
      "Rari Chain Mainnet",
      "Sonic Mainnet",
    ];
Behavior2/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 of behavioral disclosure. It describes what the tool returns (a list of networks and configurations) but lacks details about response format, pagination, rate limits, authentication requirements, or error conditions. For a tool with zero annotation coverage, this is a significant gap.

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 perfectly concise with two sentences that each earn their place. The first sentence states the core purpose, and the second provides valuable usage guidance. There is no wasted text or unnecessary elaboration.

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 complexity (simple read operation with no parameters), no annotations, and no output schema, the description is adequate but incomplete. It explains what the tool does and when to use it, but lacks details about the return format, behavioral constraints, or error handling that would be helpful for an AI agent.

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 with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters, and it doesn't add any parameter-specific information beyond what the schema already provides (which is none needed).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('list of all supported networks and their configurations'). It distinguishes from sibling tools by mentioning alternatives for more detailed information, though it doesn't explicitly differentiate from all similar tools like 'getAllNetworks'.

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

Usage Guidelines4/5

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

The description provides clear usage context by stating when to use this tool (for a list of networks and configurations) and when to use alternatives ('getAllNetworks' and 'getNetwork' for more detailed information). However, it doesn't explicitly state when NOT to use this tool or compare it to all relevant siblings.

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/crazyrabbitLTC/mcp-ethers-server'

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