bobai

bobai_activity

Read-only

Proof the tax bot (it splits the 3% tax into burns, permanent liquidity and the creator share) is actually running: last burn (with BscScan tx), burns over the last 7/30 days, total bot runs — from the public audit log, every entry verifiable on-chain. Use it to verify that burns really happen and how often; for the next buyback and whale flows use bobai_smart_money, for the burned total bobai_burned.

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_activity"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations already establish a non-destructive read, while the description adds that results come from a public audit log whose entries are verifiable on-chain, including a BscScan transaction for the last burn. It also discloses the fixed reporting windows and run count, though it does not address data freshness or behavior when no burns exist.

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 front-loads the purpose and outputs, then uses its second sentence for tool selection and alternatives; nearly every phrase carries useful information. The opening is dense, and 'Proof' is awkward wording for 'Prove,' which slightly hurts readability.

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?

For a zero-argument read-only status report, this covers the tax split being checked, the available activity evidence, reporting windows, audit-log provenance, and on-chain verification. With no output schema, naming the principal returned fields is especially useful; only minor operational details such as freshness are omitted.

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?

There are no parameters, so the empty schema leaves no input semantics to document and the baseline is 4. The description appropriately supplies the report scope without implying unsupported filters such as custom dates or wallets.

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 description identifies the resource and purpose precisely: proving the 3% tax bot is running by reporting the last burn with a BscScan transaction, burns over 7/30 days, and total bot runs. It also distinguishes the tool from bobai_smart_money and bobai_burned rather than merely restating the ambiguous tool name.

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?

It explicitly says to use the tool to verify that burns really happen and how often. It then routes next-buyback and whale-flow questions to bobai_smart_money and total-burned questions to bobai_burned, providing concrete selection boundaries.

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?