wallet-tracker

detect_bundles

Read-only

Check whether KOL wallets bought a Solana token through Jito bundles together

with side wallets they control, which hides the real size of their position.



Returns each detected bundle with a confidence score and the evidence behind

it: matching transaction fees, block index, and adjacency to the KOL's own

transaction. Use this when a user asks whether a launch was bundled,

insider-heavy, sniped or manipulated.



Solana only, because it depends on Jito bundles.



mint: the Solana token mint address

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mint`	Yes	The Solana token mint address to inspect for bundled buys.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.2/5.0

Behavior4/5

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

The description goes beyond annotations (readOnlyHint, openWorldHint) by detailing the return contents ('confidence score and evidence...') and the underlying mechanism (Jito bundles). No contradictions with annotations.

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?

The description is four sentences with no fluff: purpose, output, usage, parameter. Front-loaded and efficient. Every sentence adds value.

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 output schema present, the description doesn't need to repeat return structure. It covers purpose, usage, parameter, and expected output format. Complete enough for a simple single-parameter tool.

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 schema covers the only parameter (mint) at 100%, and the description repeats the schema's description without adding new semantic details. Baseline 3 is appropriate.

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 clearly states the tool's verb ('Check whether KOL wallets bought...') and resource ('a Solana token through Jito bundles'), with a specific purpose that distinguishes it from sibling tools like get_wallet_holdings or get_token_holders.

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 explicitly advises when to use this tool ('when a user asks whether a launch was bundled, insider-heavy...') and includes an important constraint ('Solana only'). It does not mention alternatives or when not to use, but the context is clear enough for an agent.

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

All wallet-tracker tools Inspect

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

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct function—comparing tokens vs. wallets, detecting bundles, retrieving historical vs. current signals, etc. Overlap is minimal, and descriptions clearly differentiate similar-sounding tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (compare_, detect_, get_, list_, lookup_), all in snake_case, making it easy to predict and understand the purpose of each tool.

Tool Count4/5

With 21 tools, the set is slightly above the typical 'well-scoped' range, but the breadth of functionality—covering wallet stats, tokens, signals, bundles, and comparisons across multiple blockchains—warrants the number. No tool feels redundant.

Completeness5/5

The tool surface covers essentially all aspects of wallet tracking: browsing, per-wallet stats/history/holdings/connections, token-level analysis, signals, bundles, leaderboards, and activity metrics. No obvious gaps for the stated purpose.

Resources

Need Help?