Skip to main content
Glama
Sign In

bobai

by com.brainonbnb
OverviewDiscussionsAdmin

bobai_smart_money

Read-only

Live smart-money signals for $BOBAI: the tax reserve charging the next buyback (wallet + contract queue; the queue is sold into the pool at each run and the current split buys part of it back, so this is not pure buy pressure), whale flows & holdings (auto-tracked wallets holding 0.5% of supply or more: 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. Use it to read buy pressure and what large holders do; for proof of past burns use bobai_activity, for one wallet’s balance bobai_wallet_balance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bobai_smart_money"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/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 description's added value is the caveat that the tax-reserve split 'is not pure buy pressure' and that whale wallets are auto-tracked at a 0.5%-of-supply threshold. It also notes no API key is required and that data is verifiable on-chain. A minor gap remains: no statement on refresh cadence or staleness of the live figures.

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?

Purpose is front-loaded and every clause adds substantive detail, but the single ~100-word sentence with nested parentheses is dense and forces re-reading. Minor restructure would improve it without cutting content.

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?

No output schema exists, yet the description describes each return group and its key fields (wallet+contract queue, 24h/7d in/outflows, top movers with tx, 1d/7d/30d trends, buy size/buyer/tx, burn momentum). Nothing an agent needs to decide or call it is missing.

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?

Zero parameters, so there is nothing to disambiguate; baseline 4 applies. The description correctly implies a no-argument snapshot call.

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 a specific verb+resource ('Live smart-money signals for $BOBAI') and then enumerates the four distinct payloads: tax reserve/queue, whale flows & holdings, $100+ buy ledger, and burn momentum. An agent can tell exactly what data it gets without opening the 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?

Explicitly says 'Use it to read buy pressure and what large holders do' and routes to alternatives: bobai_activity for past burn proofs, bobai_wallet_balance for a single wallet's balance. Both sibling names and the selecting condition are given.

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
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