Skip to main content
Glama
akki91
by akki91

get_token_balances_on_network

Retrieve token balances for a specific wallet address on a chosen blockchain network using Ankr API. Streamline crypto asset tracking and wallet monitoring.

Instructions

Gets all token balances for a given address on a specific network

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe address to check token balances for
networkYesThe blockchain network (e.g., "ethereum", "base")

Implementation Reference

  • The core handler function that executes the tool logic: fetches token balances from Ankr API for a wallet address on a specific network, handles authentication, API calls, and various error conditions.
    export async function getTokenBalancesOnNetwork(
      network: string,
      address: string
    ): AssetsResponse {
    
      const token = process.env.ANKR_API_TOKEN
      const endpoint = `https://rpc.ankr.com/multichain/${token}`;
     // console.log(JSON.stringify(endpoint));
    
      if (!token) {
        throw new AnkrAuthenticationError('ANKR_API_TOKEN environment variable is not set');
      }
    
    
    
      try {
    
        const data = {
          jsonrpc: "2.0",
          method: "ankr_getAccountBalance",
          params: {
            blockchain: network,
            walletAddress: address
          },
          id: 1
        };
    
        const response = await axios.post(
          endpoint,
          data,
          {
            headers: {
              'Content-Type': 'application/json',
            },
    
          }
        );
    
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          const statusCode = error.response?.status || 'unknown';
          const errorMessage = error.response?.data?.message || error.message;
          if (statusCode === 401 || statusCode === 403) {
            throw new AnkrAuthenticationError(`Authentication Failed: ${errorMessage}`);
          } else if (statusCode === 404) {
            throw new AnkrResourceNotFoundError(`Address or network not found: ${address} on ${network}`);
          } else if (statusCode === 422) {
            throw new AnkrValidationError(`Validation Error: ${errorMessage}`, error.response?.data);
          } else if (statusCode === 429) {
            const resetAt = new Date();
            resetAt.setSeconds(resetAt.getSeconds() + 60);
            throw new AnkrRateLimitError(`Rate Limit Exceeded: ${errorMessage}`, resetAt);
          }
          
          throw new Error(`Ankr API Error (${statusCode}): ${errorMessage}`);
        }
        throw new Error(`Failed to get token balances: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Zod schema defining the input parameters for the tool: network and address.
    export const TokenBalancesOnNetworkSchema = z.object({
      network: z.string().describe('The blockchain network (e.g., "ethereum", "base")'),
      address: z.string().describe('The address to check token balances for')
    });
  • src/index.ts:38-45 (registration)
    Tool registration in the ListTools handler, specifying name, description, and input schema.
    tools: [
        // Token Tools
        {
            name: "get_token_balances_on_network",
            description: "Gets all token balances for a given address on a specific network",
            inputSchema: zodToJsonSchema(tokens.TokenBalancesOnNetworkSchema)
        }
    ]
  • src/index.ts:56-65 (registration)
    Tool dispatch registration in the CallTool handler: validates input with schema and invokes the handler function.
    case "get_token_balances_on_network": {
        const args = tokens.TokenBalancesOnNetworkSchema.parse(request.params.arguments);
        const result = await tokens.getTokenBalancesOnNetwork(
            args.network,
            args.address
        );
        return {
            content: [{type: "text", text: JSON.stringify(result, null, 2)}],
        };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Gets' which implies a read operation, but fails to describe critical behaviors such as rate limits, authentication requirements, error handling, or what 'all token balances' entails (e.g., pagination, format). This leaves significant gaps for an agent.

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 any unnecessary words. It is appropriately sized and front-loaded, making it easy to parse.

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

Completeness3/5

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

Given the tool's low complexity (2 simple parameters) and no output schema, the description is minimally adequate but incomplete. It lacks details on behavioral aspects and output format, which are important for a read operation with no annotations to rely on.

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 both parameters. The description adds no additional semantic context beyond what the schema provides, such as examples or constraints, so it meets the baseline for high schema coverage.

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 ('Gets') and the resource ('all token balances for a given address on a specific network'), making the purpose specific and understandable. However, since there are no sibling tools mentioned, it cannot distinguish from alternatives, 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, prerequisites, or exclusions. It simply states what the tool does without context for usage decisions.

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

Related 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/akki91/ankr-mcp'

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