Skip to main content
Glama

fetchTokensOwnedByMultichainAddresses

Retrieve token holdings across multiple blockchain networks for specified wallet addresses using Alchemy's infrastructure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressesYesA list of wallet address and network pairs

Implementation Reference

  • index.ts:145-169 (registration)
    Registers the MCP tool 'fetchTokensOwnedByMultichainAddresses' with Zod input schema and an async handler that calls alchemyApi.getTokensByMultichainAddress and formats the response.
    server.tool('fetchTokensOwnedByMultichainAddresses', {
      addresses: z.array(z.object({
        address: z.string().describe('The wallet address to query. e.g. "0x1234567890123456789012345678901234567890"'),
        networks: z.array(z.string()).describe('The blockchain networks to query. e.g. ["eth-mainnet", "base-mainnet"]')
      })).describe('A list of wallet address and network pairs'),
    }, async (params) => {
      try {
        const result = await alchemyApi.getTokensByMultichainAddress(params);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      } catch (error) {
        if (error instanceof Error) {
          console.error('Error in getTokensByMultichainAddress:', error);
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true
          };
        }
        return {
          content: [{ type: "text", text: 'Unknown error occurred' }],
          isError: true
        };
      }
    });
  • Core implementation of the tool logic: creates Alchemy multi-chain token client, posts request to /by-address endpoint, processes response by converting hex balances to decimals using helper.
    async getTokensByMultichainAddress(params: MultiChainTokenByAddress) {
      try {
        const client = createMultiChainTokenClient();
        
        const response = await client.post('/by-address', {
          addresses: params.addresses.map((pair: AddressPair) => ({
            address: pair.address,
            networks: pair.networks
          }))
        });
    
        const responseData = convertHexBalanceToDecimal(response);
        return responseData;
      } catch (error) {
        console.error('Error fetching token data:', error);
        throw error;
      }
    },
  • Zod schema defining the input parameters for the tool: array of address-network pairs.
    addresses: z.array(z.object({
      address: z.string().describe('The wallet address to query. e.g. "0x1234567890123456789012345678901234567890"'),
      networks: z.array(z.string()).describe('The blockchain networks to query. e.g. ["eth-mainnet", "base-mainnet"]')
    })).describe('A list of wallet address and network pairs'),
  • TypeScript interface defining the input type MultiChainTokenByAddress used in alchemyApi.
    export interface MultiChainTokenByAddress {
      addresses: AddressPair[];
    }
  • Helper utility that converts hexadecimal token balances from Alchemy API response to readable decimal values, handling token decimals.
    export default function convertHexBalanceToDecimal(response: any) {
        // Handle nested data structure - API returns { data: { data: { tokens: [...] } } }
        const responseData = response.data && response.data.data ? response.data.data : response.data;
            
        // Process tokens if they exist
        // LLMs are very bad at arithmetic, so we need to convert the hex balances to decimal
        if (responseData.tokens && Array.isArray(responseData.tokens)) {
          // Convert hex balances to decimal
          responseData.tokens = responseData.tokens.map((token: any) => {
            try {
              const processedToken = { ...token };
              const hexTokenBalance = token.tokenBalance;
              const tokenDecimals = parseInt(token.tokenMetadata.decimals || '18', 10);
              
              const bigIntBalance = BigInt(hexTokenBalance);
              const decimalBalance = Number(bigIntBalance) / Math.pow(10, tokenDecimals);
              
              // Store both formats
              processedToken.originalHexBalance = hexTokenBalance;
              processedToken.tokenBalance = decimalBalance;
              
              return processedToken;
            } catch (error) {
              // On error, return token with balance as 0 but keep original hex
              return {
                ...token,
                originalHexBalance: token.tokenBalance,
                tokenBalance: 0
              };
            }
          });
        }
      
        return responseData;
      }
  • Helper function that creates configured axios client for Alchemy's multi-chain tokens API endpoint.
    export const createMultiChainTokenClient = () => axios.create({
      baseURL: `https://api.g.alchemy.com/data/v1/${API_KEY}/assets/tokens`,
      headers: {
          'accept': 'application/json',
          'content-type': 'application/json',
          'x-alchemy-client-breadcrumb': BREADCRUMB_HEADER
      },
    });
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/alchemyplatform/alchemy-mcp-server'

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