Skip to main content
Glama

network_get_network

Retrieve the current network details for the MCP Crypto Wallet EVM, providing essential blockchain information for wallet management and transactions.

Instructions

Get the current network information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for 'network_get_network'. It retrieves the current provider and calls provider.getNetwork() to fetch network details like name, chain ID, and ENS address, formatting the response.
    export const getNetworkHandler = async (input: any): Promise<ToolResultSchema> => {
      try {
        const provider = getProvider();
        if (!provider) {
          return createErrorResponse("Provider is required to get network information, please set the provider URL");
        }
        const network = await provider.getNetwork();
    
        return createSuccessResponse(`Network information retrieved successfully
          Network name: ${network.name}
          Chain ID: ${network.chainId}
          ENS address: ${network.ensAddress}
        `);
      } catch (error) {
        return createErrorResponse(`Failed to get network information: ${(error as Error).message}`);
      }
    };
  • The tool schema definition in the tools array, specifying name, description, and empty input schema (no parameters required).
    {
      name: "network_get_network",
      description: "Get the current network information",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • src/tools.ts:602-602 (registration)
    Registration of the tool handler in the handlers dictionary, mapping 'network_get_network' to getNetworkHandler.
    "network_get_network": getNetworkHandler,
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read-only operation ('get'), but doesn't disclose behavioral traits like whether it requires authentication, has rate limits, or what format the network information is returned in (e.g., JSON object with fields). This is a significant gap for a tool with zero annotation coverage.

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 a single, efficient sentence with no wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the lack of annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't clarify what 'network information' includes (e.g., chain ID, network name, RPC URL) or how it differs from other network-related tools, leaving the agent with insufficient context to use it effectively.

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 parameter details, which is appropriate here, but a baseline of 4 is given since it doesn't compensate for any gaps (there are none).

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

Purpose3/5

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

The description 'Get the current network information' clearly states the action (get) and resource (network information), but it's vague about what specific network information is retrieved. It doesn't distinguish from siblings like 'network_get_block_number' or 'provider_get_chain_id', which also provide network-related data.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'network_get_block_number' and 'provider_get_chain_id', the description lacks context on whether this tool returns broader network details (e.g., chain ID, name) or something else, leaving the agent to guess.

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/dcSpark/mcp-cryptowallet-evm'

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