Skip to main content
Glama

bobai

by com.brainonbnb

bsc_pool_scan

Read-only

Measure what a trade on BNB Smart Chain would actually cost, for ANY token or pool — before placing it. Reads the pool live from the chain and returns: real cost per trade size (price impact + swap fee + transfer tax together, not the headline slippage a router shows), the USD size that moves the price 1% in each direction, the transfer tax MEASURED from executed trades rather than taken from a label, how much of the token's liquidity the readable pool actually holds, and whether the LP is burned or still withdrawable. Works on PancakeSwap V2/V3, Uniswap V2 and Biswap. No API key, nothing cached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesA BSC token address, a pool/pair address, or any BscScan / DexScreener / PancakeSwap link containing one

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark it read-only, and the description adds meaningful behavioral context: it reads live pool state, measures transfer tax from executed trades rather than labels, reports whether LP is burned or withdrawable, and uses no API key or cache. This gives the agent a clear operational model beyond the readOnlyHint.

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?

Although the description is long, every clause earns its place: exact outputs, measured tax, live reads, supported protocols, and no caching. It front-loads the core purpose and uses a clear return list, making the length justified.

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

Completeness5/5

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

With a single well-documented parameter, read-only annotations, no output schema, and no nested objects, the description covers purpose, acceptable inputs, return contents, supported protocols, and data source. There is no critical missing information for correct invocation or output interpretation.

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 already documents the single address parameter with 100% coverage, including token addresses, pool addresses, and supported links, so the baseline is 3. The description adds general scope like 'ANY token or pool' but no new syntax, defaults, or edge-case details for the parameter itself.

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?

The first sentence names a precise verb-resource pair: measuring actual trade cost on BNB Smart Chain for any token or pool before placing a trade. The detailed return list and supported DEXes make its purpose unmistakable and clearly distinguish it from siblings like bobai_token_info or bobai_liquidity.

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

Usage Guidelines4/5

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

The description clearly signals when to use it: before placing a trade, for any BSC token or pool, and specifically on PancakeSwap V2/V3, Uniswap V2, and Biswap. It does not explicitly name alternatives or state when not to use it, so it stops short of full routing guidance.

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