Skip to main content
Glama

erc1155_balanceOfBatch

Query multiple ERC1155 token balances for different addresses and token IDs in a single blockchain call to efficiently check ownership across collections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenAddressYesThe address of the ERC1155 contract
ownerAddressesYesArray of addresses to check balances for
tokenIdsYesArray of token IDs to check balances for
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.

Implementation Reference

  • Registration of the erc1155_balanceOfBatch tool including inline schema and handler function. This is where the tool is defined and registered with the MCP server.
      "erc1155_balanceOfBatch",
      {
        tokenAddress: contractAddressSchema,
        ownerAddresses: z.array(addressSchema).describe(
          "Array of addresses to check balances for"
        ),
        tokenIds: z.array(tokenIdSchema).describe(
          "Array of token IDs to check balances for"
        ),
        provider: providerSchema,
        chainId: chainIdSchema
      },
      async (params) => {
        try {
          const balances = await ethersService.getERC1155BatchBalances(
            params.tokenAddress,
            params.ownerAddresses,
            params.tokenIds,
            params.provider,
            params.chainId
          );
          
          let resultText = "Batch balances:\n";
          for (let i = 0; i < params.ownerAddresses.length; i++) {
            resultText += `${params.ownerAddresses[i]} - Token ${params.tokenIds[i]}: ${balances[i]}\n`;
          }
          
          return {
            content: [{ 
              type: "text", 
              text: resultText
            }]
          };
        } catch (error) {
          return {
            isError: true,
            content: [{ 
              type: "text", 
              text: `Error getting ERC1155 batch balances: ${error instanceof Error ? error.message : String(error)}`
            }]
          };
        }
      }
    );
  • The handler function that executes the tool: fetches batch balances using EthersService and formats the response as text.
    async (params) => {
      try {
        const balances = await ethersService.getERC1155BatchBalances(
          params.tokenAddress,
          params.ownerAddresses,
          params.tokenIds,
          params.provider,
          params.chainId
        );
        
        let resultText = "Batch balances:\n";
        for (let i = 0; i < params.ownerAddresses.length; i++) {
          resultText += `${params.ownerAddresses[i]} - Token ${params.tokenIds[i]}: ${balances[i]}\n`;
        }
        
        return {
          content: [{ 
            type: "text", 
            text: resultText
          }]
        };
      } catch (error) {
        return {
          isError: true,
          content: [{ 
            type: "text", 
            text: `Error getting ERC1155 batch balances: ${error instanceof Error ? error.message : String(error)}`
          }]
        };
      }
    }
  • Zod schema defining input parameters for the tool: contract address, arrays of owners and token IDs, optional provider and chainId.
      tokenAddress: contractAddressSchema,
      ownerAddresses: z.array(addressSchema).describe(
        "Array of addresses to check balances for"
      ),
      tokenIds: z.array(tokenIdSchema).describe(
        "Array of token IDs to check balances for"
      ),
      provider: providerSchema,
      chainId: chainIdSchema
    },
  • Helper function balanceOfBatch that implements the core ERC1155 balanceOfBatch contract call with caching, metrics, error handling. Likely called by EthersService.getERC1155BatchBalances.
    export async function balanceOfBatch(
      ethersService: EthersService,
      contractAddress: string,
      ownerAddresses: string[],
      tokenIds: (string | number)[],
      provider?: string,
      chainId?: number
    ): Promise<string[]> {
      metrics.incrementCounter('erc1155.balanceOfBatch');
      
      return timeAsync('erc1155.balanceOfBatch', async () => {
        try {
          // Validate input lengths
          if (ownerAddresses.length !== tokenIds.length) {
            throw new ERC1155Error(
              'Owner addresses and token IDs arrays must have the same length'
            );
          }
          
          // Get provider from ethers service
          const ethersProvider = ethersService['getProvider'](provider, chainId);
          
          // Create contract instance
          const contract = new ethers.Contract(contractAddress, ERC1155_ABI, ethersProvider);
          
          // Get balances
          const balances = await contract.balanceOfBatch(ownerAddresses, tokenIds);
          
          // Convert to strings
          return balances.map((balance: bigint) => balance.toString());
        } catch (error) {
          logger.debug('Error getting ERC1155 batch balances', { contractAddress, error });
          throw handleTokenError(error, 'Failed to get token balances');
        }
      });
    }
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