Skip to main content
Glama

getWalletBalance

Retrieve the current Ether balance for any Ethereum wallet address across supported networks. Specify an address and optionally a network or chain ID to query blockchain data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe Ethereum address to query
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

  • Handler function that fetches the ETH balance for the given address using the selected provider's getBalance method, formats it to ETH and wei, and returns a text response. Uses ethersService for provider selection and handles errors.
    async ({ address, provider, chainId }) => { try { // Get the balance in wei directly from the provider const selectedProvider = provider ? ethersService.getProvider(provider, chainId) : ethersService.provider; const balanceWei = await selectedProvider.getBalance(address); const balanceEth = ethers.formatEther(balanceWei); return { content: [{ type: "text", text: `Balance of ${address}: ${balanceEth} ETH (${balanceWei.toString()} wei)` }] }; } catch (error) { return createErrorResponse(error, 'getting wallet balance'); } }
  • Zod input schema for the getWalletBalance tool. Requires an Ethereum address; optional provider (network name or RPC URL) and chainId.
    { address: addressSchema.describe( "The Ethereum address to query" ), 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." ) },
  • Registration of the getWalletBalance tool using server.tool() within the registerCoreTools function, including inline schema and handler.
    server.tool( "getWalletBalance", { address: addressSchema.describe( "The Ethereum address to query" ), 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 ({ address, provider, chainId }) => { try { // Get the balance in wei directly from the provider const selectedProvider = provider ? ethersService.getProvider(provider, chainId) : ethersService.provider; const balanceWei = await selectedProvider.getBalance(address); const balanceEth = ethers.formatEther(balanceWei); return { content: [{ type: "text", text: `Balance of ${address}: ${balanceEth} ETH (${balanceWei.toString()} wei)` }] }; } catch (error) { return createErrorResponse(error, 'getting wallet balance'); } } );

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