Skip to main content
Glama

getWalletInfo

Retrieve detailed wallet information for any Binance Smart Chain address, including balances and transaction history, using the BSC MCP Server API.

Instructions

Get wallet info for an address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressNo

Implementation Reference

  • The core handler function for the 'Get_Wallet_Info' tool. Fetches balance for the provided or user's own wallet address using getBalance helper, formats native BNB balance, token balances, and address into text content, or returns error response.
    async ({ address }) => {
      try {
        if (address === '' || !address || address === 'null') {
          const account = await getAccount();
          address = account.address
        }
        const balance = await getBalance(address);
    
        return {
          content: [
            {
              type: "text",
              text: `Native Balance (BNB): ${balance.nativeBalance}\n\nToken Balances:\n${JSON.stringify(balance.tokenBalances)}\n\nWallet Address: ${address}`,
            },
          ],
        };
      } catch (error) {
        const errorMessage =
          error instanceof Error ? error.message : String(error);
        return {
          content: [
            { type: "text", text: `Failed to fetch balance: ${errorMessage}` },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema for the tool: optional 'address' string parameter for the wallet address to query.
    address: z.string().optional().describe("When querying the user's own wallet value, it is null"),
  • Registration function for the 'Get_Wallet_Info' tool, called by main.ts. Registers the tool on the McpServer with name, description, input schema, and handler function.
    export function registerGetWalletInfo(server: McpServer) {
      server.tool("Get_Wallet_Info", "👛View detailed balance and holdings for any wallet address", {
          address: z.string().optional().describe("When querying the user's own wallet value, it is null"),
        },
        async ({ address }) => {
          try {
            if (address === '' || !address || address === 'null') {
              const account = await getAccount();
              address = account.address
            }
            const balance = await getBalance(address);
    
            return {
              content: [
                {
                  type: "text",
                  text: `Native Balance (BNB): ${balance.nativeBalance}\n\nToken Balances:\n${JSON.stringify(balance.tokenBalances)}\n\nWallet Address: ${address}`,
                },
              ],
            };
          } catch (error) {
            const errorMessage =
              error instanceof Error ? error.message : String(error);
            return {
              content: [
                { type: "text", text: `Failed to fetch balance: ${errorMessage}` },
              ],
              isError: true,
            };
          }
        }
      );
    }
  • src/main.ts:30-30 (registration)
    Call to registerGetWalletInfo during MCP server initialization, integrating the tool into the server.
    registerGetWalletInfo(server);
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't cover aspects like read-only nature, error handling, rate limits, or what 'wallet info' includes, which is insufficient for a tool with no structured safety hints.

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 with zero waste, making it appropriately sized and front-loaded. Every word contributes directly to stating the tool's purpose.

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 tool's complexity (1 parameter, no annotations, no output schema), the description is incomplete. It lacks details on behavior, parameter usage, and output format, failing to provide enough context for effective agent use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but adds no meaning beyond the schema. It mentions 'address' but doesn't explain its format, constraints, or if it's required, leaving the single parameter poorly defined.

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') and resource ('wallet info for an address'), making the purpose understandable. However, it doesn't differentiate from siblings like 'securityCheck' or 'pancakeMyPosition' that might also retrieve wallet-related data, so it's not fully specific.

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 prerequisites, such as needing a valid address, or compare it to siblings like 'securityCheck' for wallet security info, leaving usage context unclear.

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/TermiX-official/bsc-mcp'

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