Skip to main content
Glama

check-balance

Check the ETH balance of an Ethereum address on chain-id 175. Enter a valid 0x format address to view current holdings.

Instructions

Check the ETH balance of an Ethereum address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesEthereum address (0x format)

Implementation Reference

  • Executes the check-balance tool: validates address input, fetches balance from service, formats and returns response.
    if (name === "check-balance") {
      try {
        const { address } = AddressSchema.parse(args);
        const balance = await etherscanService.getAddressBalance(address);
        const response = `Address: ${balance.address}\nBalance: ${balance.balanceInEth} ETH`;
        return {
          content: [{ type: "text", text: response }],
        };
      } catch (error) {
        if (error instanceof z.ZodError) {
          throw new Error(`Invalid input: ${error.errors.map(e => e.message).join(", ")}`);
        }
        throw error;
      }
    }
  • Zod schema for validating the Ethereum address input parameter.
    const AddressSchema = z.object({
      address: z.string().regex(/^0x[a-fA-F0-9]{40}$/, 'Invalid Ethereum address format'),
    });
  • src/server.ts:55-69 (registration)
    Registers the check-balance tool in the listTools response with description and input schema.
    {
      name: "check-balance",
      description: "Check the ETH balance of an Ethereum address",
      inputSchema: {
        type: "object",
        properties: {
          address: {
            type: "string",
            description: "Ethereum address (0x format)",
            pattern: "^0x[a-fA-F0-9]{40}$"
          },
        },
        required: ["address"],
      },
    },
  • Fetches the ETH balance for a given address using EtherscanProvider, validates address, converts wei to ETH.
    async getAddressBalance(address: string): Promise<{
      address: string;
      balanceInWei: bigint;
      balanceInEth: string;
    }> {
      try {
        // Validate the address
        const validAddress = ethers.getAddress(address);
        
        // Get balance in Wei
        const balanceInWei = await this.provider.getBalance(validAddress);
        
        // Convert to ETH
        const balanceInEth = ethers.formatEther(balanceInWei);
    
        return {
          address: validAddress,
          balanceInWei,
          balanceInEth
        };
      } catch (error) {
        if (error instanceof Error) {
          throw new Error(`Failed to get balance: ${error.message}`);
        }
        throw error;
      }
    }
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 what the tool does but doesn't describe any behavioral traits such as whether it's read-only, requires authentication, has rate limits, or what the output format looks like. This is inadequate for a tool with zero annotation coverage.

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 wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 incomplete. It doesn't explain what the tool returns (e.g., balance in wei or ETH), potential error conditions, or behavioral aspects like network dependencies. For a tool with no structured data beyond the input schema, this leaves significant gaps.

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, with the 'address' parameter fully documented in the schema. The description adds no additional meaning beyond what's in the schema, such as clarifying the address format or providing examples. Baseline 3 is appropriate when the schema does all the work.

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 ('Check') and resource ('ETH balance of an Ethereum address'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get-token-transfers' or 'get-transactions' that might also involve balance-related queries, so it doesn't reach the highest 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. It doesn't mention sibling tools like 'get-token-transfers' for token-specific balances or clarify that this is specifically for native ETH balance. There's no context about prerequisites or exclusions.

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/otc-ai/mcp-otc'

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