Brain On BNB AI ($BOBAI)

bobai_wallet_balance

Read-only

Get the BNB and $BOBAI balance for any BSC wallet address to verify holdings before or after a trade. For whale flows across many wallets, use bobai_smart_money.

Instructions

BNB and $BOBAI balance of any BSC wallet address. Use it to check one wallet before or after a trade; for whale flows across many wallets use bobai_smart_money.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "bobai_wallet_balance"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	BSC wallet address (0x + 40 hex chars)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful scope context (single-wallet lookup vs aggregate flows), though it does not state the return format or units, which would help for a balance call with no output schema.

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?

Two tight sentences, zero filler, with the scope constraint and the sibling routing front-loaded. Every clause earns its place.

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

Completeness4/5

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

For a one-parameter read-only lookup the description is nearly complete, and it names the returned assets. Because there is no output schema, the description could still be stronger on return shape (units, decimals, formatting), which is the only remaining gap.

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?

Schema description coverage is 100% and the single address param is fully documented in the schema (0x + 40 hex chars). The description adds no syntax or format detail beyond what the schema already provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the exact resources returned (BNB and $BOBAI balances) for a specific scope (any BSC wallet address), which is a precise verb-free but unambiguous resource statement. It is clearly distinguishable from siblings like bobai_smart_money and bobai_token_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use it to check one wallet before or after a trade, and names the alternative (bobai_smart_money) with the condition (whale flows across many wallets) that selects it instead. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.