bobai

bobai_wallet_balance

Read-only

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.

Changed1 schema field changedNov 11, 2026
- addedInput schema / properties / address / examples
```
Added value: +[
+  "0xdeFC0e900Dfc83e207902cF22265Ae63f94c01ce"
+]
```
First observedJul 3, 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 that both native BNB and token balance are returned for an arbitrary address. It stops short of noting error behavior for malformed or non-BSC addresses, or any rate limits, which keeps it off a 5.

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 short sentences, front-loaded with what is returned, followed by routing guidance. Every clause carries information; nothing is redundant padding.

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?

A single-parameter read tool with no output schema needs little, and the description names the returned values and the correct context of use. It does not specify behavior on invalid addresses or chains outside BSC, a minor gap rather than a blocking one.

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% — the address parameter already documents format (0x + 40 hex chars) and includes an example. The description only reinforces 'any BSC wallet address', which is consistent with but not additive to the schema, so the baseline of 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 precisely what is returned (BNB and $BOBAI balances) and for which resource (any BSC wallet address), which is a specific capability rather than a restatement of the name. It also distinguishes itself from bobai_smart_money, so an agent can tell the two apart without opening either schema.

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?

Gives an explicit use case (checking one wallet before or after a trade) and an explicit exclusion with the alternative to use instead (multi-wallet whale flows go to bobai_smart_money). The selection condition between the two tools is stated, not left to inference.

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

All bobai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?