Skip to main content
Glama

get_supported_networks

Retrieve a list of supported EVM networks through the EVM MCP Server, simplifying integration with 30+ Ethereum-compatible blockchains for token transfers, contract interactions, and ENS resolution.

Instructions

Get a list of supported EVM networks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function registered for the MCP tool 'get_supported_networks'. It calls getSupportedNetworks(), formats the result as JSON text content, and handles errors.
    async () => {
      try {
        const networks = getSupportedNetworks();
        return {
          content: [{ type: "text", text: JSON.stringify({ supportedNetworks: networks }, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
          isError: true
        };
      }
    }
  • The input schema (empty object), description, and annotations for the 'get_supported_networks' tool.
    {
      description: "Get a list of all supported EVM networks",
      inputSchema: {},
      annotations: {
        title: "Get Supported Networks",
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false
      }
    },
  • The server.registerTool call that registers the 'get_supported_networks' tool with its schema and handler.
    server.registerTool(
      "get_supported_networks",
      {
        description: "Get a list of all supported EVM networks",
        inputSchema: {},
        annotations: {
          title: "Get Supported Networks",
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false
        }
      },
      async () => {
        try {
          const networks = getSupportedNetworks();
          return {
            content: [{ type: "text", text: JSON.stringify({ supportedNetworks: networks }, null, 2) }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
            isError: true
          };
        }
      }
    );
  • The core utility function getSupportedNetworks() that extracts and sorts the list of supported network names from the networkNameMap, excluding short aliases like 'eth' or 'op'.
    export function getSupportedNetworks(): string[] {
      return Object.keys(networkNameMap)
        .filter(name => name.length > 2) // Filter out short aliases
        .sort();
    } 
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get a list' implies a read-only operation, it doesn't specify whether this requires authentication, what format the list returns, whether it's cached or real-time, or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 - a single sentence that communicates the essential purpose without any wasted words. It's front-loaded with the core action and resource. Every word earns its place, making this an excellent example of efficient documentation.

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?

For a simple read-only tool with zero parameters and no output schema, the description provides the minimum viable information. However, without annotations or output schema, it should ideally specify what format the list returns (e.g., array of network names/IDs) or typical use cases. The description is adequate but leaves room for improvement regarding the return value.

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 zero parameters, and schema description coverage is 100% (since there are no parameters to describe). The description appropriately doesn't waste space discussing nonexistent parameters. A baseline of 4 is appropriate for zero-parameter tools where the schema fully covers the parameter space.

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 verb ('Get') and resource ('list of supported EVM networks'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'get_chain_info', but the specificity of 'supported EVM networks' provides reasonable distinction. The description avoids tautology by not just repeating the tool name.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_chain_info' or other network-related tools. There's no mention of prerequisites, typical use cases, or when this tool would be preferred over other methods of obtaining network information. The agent must infer usage from the tool name alone.

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

Related 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/mcpdotdirect/evm-mcp-server'

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