Skip to main content
Glama

bobai

by com.brainonbnb

bobai_smart_money

Read-only

Live smart-money signals for $BOBAI: the tax reserve charging the next buyback (wallet + contract queue = pending buy pressure), whale flows & holdings (auto-tracked 1%-of-supply wallets: 24h/7d in/outflows, top movers with tx, daily balance snapshots with 1d/7d/30d holdings trends), an immutable on-chain ledger of recent $100+ buys (size, buyer wallet, tx), and burn momentum. All verifiable, no API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: 'Live', 'auto-tracked', 'immutable on-chain ledger', and 'All verifiable, no API key', which go beyond the annotations and tell the agent about freshness, provenance, and access requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well-structured, with the core purpose front-loaded ('Live smart-money signals for $BOBAI') followed by clearly separated data categories. Every clause adds a distinct signal type or timeframe, so there is little filler even though the sentence is long.

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?

With no output schema present, the description carries the burden of explaining what the tool returns. It covers concrete metrics and timeframes: 24h/7d in/outflows, top movers with tx, 1d/7d/30d holdings trends, and $100+ buy ledger entries. It is complete enough for an agent to know what to expect, though exact response formatting is not specified.

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

Parameters4/5

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

The tool has zero parameters and schema description coverage is 100%, so there are no parameter meanings left to document. The description appropriately focuses on the data the tool returns rather than input semantics.

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 states that the tool provides live smart-money signals for $BOBAI and enumerates the signal categories: tax reserve/buyback pressure, whale flows and holdings, recent $100+ buys, and burn momentum. It is specific to the token and its content, though it does not explicitly differentiate itself from related siblings like bobai_price or bobai_burned.

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?

There is no guidance about when to use this tool versus the many sibling tools. The description implies usefulness for whale/smart-money tracking but never states explicit alternatives, exclusions, or a decision rule for selection.

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

All bobai toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

Several tools operate on overlapping data: bobai_burned, bobai_activity, and bobai_smart_money all report burn-related metrics, while bobai_token_info, bobai_circulating_supply, and bobai_burned overlap on supply numbers. The long descriptions mitigate this, but the purpose boundaries are less crisp than ideal. The BSC pool tools are more easily told apart.

Naming Consistency3/5

Most token tools use a consistent bobai_* snake_case prefix, but the set mixes conventions: bnb_agent_*, bsc_pool_scan, find_agents_on_bnb_chain, and pancakeswap_fee_tiers break the pattern. The names are still readable and mostly noun-oriented. There is no chaotic mixing of camelCase or vague verbs, but the pattern is not uniform.

Tool Count3/5

19 tools sits in the borderline heavy range for a token research server. Many are focused data views, but some could be consolidated, such as bobai_token_info with circulating supply/burned, or the informational guide/links/tokenomics cluster. Each tool has a defensible role, but the overall surface feels padded.

Completeness4/5

Core workflows are well covered: price, liquidity, DEX parameters, purchase guidance, burns, wallet balances, and BNB agent discovery. Missing historical price/volume, holder distributions, or detailed per-agent profiles, but these are minor gaps rather than dead ends. The server gives an agent what it needs to understand and interact with $BOBAI.

Resources