Skip to main content
Glama

get-chain-id

Retrieve the current blockchain network identifier from MetaMask to verify connection and ensure correct network operations.

Instructions

Get the current chain id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that implements the 'get-chain-id' tool logic by calling getChainId from wagmi/core and formatting the result as MCP text content.
    execute: async () => {
      const result = getChainId(wagmiConfig);
      return {
        content: [
          {
            type: "text",
            text: result.toString(),
          },
        ],
      };
    },
  • Input schema using Zod: empty object, indicating no parameters required for the tool.
    parameters: z.object({}),
  • The registration function for the 'get-chain-id' tool, which adds the tool to the FastMCP server with name, description, schema, and handler.
    export function registerGetChainIdTools(server: FastMCP, wagmiConfig: Config): void {
      server.addTool({
        name: "get-chain-id",
        description: "Get the current chain id.",
        parameters: z.object({}),
        execute: async () => {
          const result = getChainId(wagmiConfig);
          return {
            content: [
              {
                type: "text",
                text: result.toString(),
              },
            ],
          };
        },
      });
    };
  • Calls the specific registration function for 'get-chain-id' tool within the overall registerTools function.
    registerGetChainIdTools(server, wagmiConfig);
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. It states the action ('Get') but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires network connectivity, potential errors, or response format. For a tool with zero annotation coverage, this is insufficient.

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, clear sentence with no wasted words. It's front-loaded and efficiently conveys the core purpose without unnecessary elaboration.

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 complexity (simple read operation) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'chain id' means in this context, the return value, or any error conditions, leaving gaps for the agent to infer.

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 the schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for 0 parameters is 4, as the description doesn't need to compensate for any gaps.

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 'Get the current chain id' clearly states the verb ('Get') and resource ('current chain id'), making the purpose immediately understandable. However, it doesn't differentiate from siblings like 'get-chain-list' or 'get-chains' which might return multiple chains or chain information, so it's not a perfect 5.

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-list' or 'get-chains', nor does it mention any prerequisites or context for usage. It's a basic statement of function without operational context.

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/Xiawpohr/metamask-mcp'

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