Skip to main content
Glama

contractCall

Execute smart contract functions on Ethereum networks by specifying contract address, ABI, and method parameters to interact with blockchain applications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contractAddressYesThe address of the contract to call
abiYesThe ABI of the contract function to call, in JSON format
methodYesThe name of the method to call
argsNoOptional. The arguments to pass to the contract function
providerNoOptional. Either a network name or custom RPC URL. Use getAllNetworks to see available networks and their details, or getNetwork to get info about a specific network. You can use any network name returned by these tools as a provider value.
chainIdNoOptional. The chain ID to use. If provided with a named network and they don't match, the RPC's chain ID will be used.

Implementation Reference

  • Registers the 'contractCall' tool with the MCP server, including schema and handler function.
    server.tool(
      "contractCall",
      {
        contractAddress: z.string().describe(
          "The address of the contract to call"
        ),
        abi: z.string().describe(
          "The ABI of the contract function to call, in JSON format"
        ),
        method: z.string().describe(
          "The name of the method to call"
        ),
        args: z.array(z.any()).optional().describe(
          "Optional. The arguments to pass to the contract function"
        ),
        provider: z.string().optional().describe(PROVIDER_DESCRIPTION),
        chainId: z.number().optional().describe(
          "Optional. The chain ID to use. If provided with a named network and they don't match, the RPC's chain ID will be used."
        )
      },
      async ({ contractAddress, abi, method, args = [], provider, chainId }) => {
        try {
          const result = await ethersService.contractCallView(
            contractAddress,
            abi,
            method,
            args,
            provider,
            chainId
          );
          
          // Format the result
          let formattedResult = '';
          if (result === null || result === undefined) {
            formattedResult = 'null';
          } else if (typeof result === 'object') {
            formattedResult = JSON.stringify(result, null, 2);
          } else {
            formattedResult = String(result);
          }
          
          return {
            content: [{ 
              type: "text", 
              text: formattedResult
            }]
          };
        } catch (error) {
          return {
            isError: true,
            content: [{ 
              type: "text", 
              text: `Error calling contract function: ${error instanceof Error ? error.message : String(error)}`
            }]
          };
        }
      }
    );
  • The handler function that performs the contractCall by invoking ethersService.contractCallView with the input parameters, formats the result, and returns it as MCP content.
    async ({ contractAddress, abi, method, args = [], provider, chainId }) => {
      try {
        const result = await ethersService.contractCallView(
          contractAddress,
          abi,
          method,
          args,
          provider,
          chainId
        );
        
        // Format the result
        let formattedResult = '';
        if (result === null || result === undefined) {
          formattedResult = 'null';
        } else if (typeof result === 'object') {
          formattedResult = JSON.stringify(result, null, 2);
        } else {
          formattedResult = String(result);
        }
        
        return {
          content: [{ 
            type: "text", 
            text: formattedResult
          }]
        };
      } catch (error) {
        return {
          isError: true,
          content: [{ 
            type: "text", 
            text: `Error calling contract function: ${error instanceof Error ? error.message : String(error)}`
          }]
        };
      }
    }
  • Zod schema defining the input parameters for the contractCall tool: contractAddress, abi, method, optional args, provider, and chainId.
    {
      contractAddress: z.string().describe(
        "The address of the contract to call"
      ),
      abi: z.string().describe(
        "The ABI of the contract function to call, in JSON format"
      ),
      method: z.string().describe(
        "The name of the method to call"
      ),
      args: z.array(z.any()).optional().describe(
        "Optional. The arguments to pass to the contract function"
      ),
      provider: z.string().optional().describe(PROVIDER_DESCRIPTION),
      chainId: z.number().optional().describe(
        "Optional. The chain ID to use. If provided with a named network and they don't match, the RPC's chain ID will be used."
      )
    },
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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