Skip to main content
Glama

get_token_balance

Check token balance for any address on supported blockchain networks by providing chain ID, token address, and wallet address.

Instructions

Get the balance of a specific token for a specific address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chain_idYesThe chain ID
token_addressYesThe address of the token
addressYesThe address to check the balance for

Implementation Reference

  • The handler function that implements the core logic for the 'get_token_balance' tool by querying the Etherscan API for the token balance of a given address on a specific chain.
    async function handleGetTokenBalance(req: any, apiKey: string) {
        const chainId = req.params.arguments.chain_id;
        const tokenAddress = req.params.arguments.token_address;
        const address = req.params.arguments.address;
    
        try {
            const response = await axios.get(
                `https://api.etherscan.io/v2/api?chainid=${chainId}&module=account&action=tokenbalance&contractaddress=${tokenAddress}&address=${address}&tag=latest&apikey=${apiKey}`
            );
    
            if (response.data.status === "1") {
                const balance = response.data.result;
                return {
                    content: [
                        {
                            type: "text",
                            text: `Balance of token ${tokenAddress} for address ${address} on chain ${chainId}: ${balance}`,
                        },
                    ],
                };
            } else {
                return {
                    content: [
                        {
                            type: "text",
                            text: `Failed to get token balance: ${response.data.message}`,
                        },
                    ],
                };
            }
        } catch (error) {
            return {
                content: [
                    {
                        type: "text",
                        text: `Failed to get token balance: ${error}`,
                    },
                ],
            };
        }
    }
  • The ToolDefinition object defining the input schema, name, and description for the 'get_token_balance' tool.
    const getTokenBalance: ToolDefinition = {
        name: "get_token_balance",
        description: "Get the balance of a specific token for a specific address",
        inputSchema: {
            type: "object",
            properties: {
                chain_id: {
                    type: "integer",
                    description: "The chain ID",
                },
                token_address: {
                    type: "string",
                    description: "The address of the token",
                },
                address: {
                    type: "string",
                    description: "The address to check the balance for",
                },
            },
            required: ["chain_id", "token_address", "address"],
        },
    };
  • index.ts:216-223 (registration)
    The toolDefinitions map where 'get_token_balance' is registered by including getTokenBalance in the tools object.
    const toolDefinitions: { [key: string]: ToolDefinition } = {
        [getFilteredRpcList.name]: getFilteredRpcList,
        [getChainId.name]: getChainId,
        [getTotalSupply.name]: getTotalSupply,
        [getTokenBalance.name]: getTokenBalance,
        [getTokenHolders.name]: getTokenHolders,
        [getTokenHoldersCount.name]: getTokenHoldersCount
    };
  • index.ts:485-486 (registration)
    The switch case in the callToolHandler that dispatches calls to the 'get_token_balance' handler.
    case getTokenBalance.name:
        return await handleGetTokenBalance(req, apiKey);
  • index.ts:509-511 (registration)
    The server capabilities section where the toolDefinitions (including 'get_token_balance') are registered with the MCP server.
    capabilities: {
        tools: toolDefinitions,
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool's function but omits critical details like whether it's a read-only operation, potential rate limits, error conditions (e.g., invalid addresses), or the format of the returned balance. This leaves significant gaps in understanding how the tool behaves.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action, making it easy to parse and understand quickly.

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 lack of annotations and output schema, the description is insufficient for a tool with three required parameters. It doesn't explain what the balance output looks like (e.g., numeric value, units) or address common use cases, leaving the agent with incomplete context for effective tool invocation.

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

Parameters3/5

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

The input schema has 100% description coverage, clearly documenting all three parameters. The description adds no additional semantic context beyond what the schema provides, such as examples or constraints (e.g., address formats). This meets the baseline for high schema coverage but doesn't enhance parameter understanding.

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 clearly states the action ('Get the balance') and resource ('of a specific token for a specific address'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_token_holders' or 'get_total_supply', which prevents a perfect score.

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_token_holders' or 'get_total_supply'. It lacks context about prerequisites, such as whether the token must be deployed on the specified chain, leaving the agent to infer usage scenarios.

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/septemhill/etherscan-mcp'

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