Skip to main content
Glama

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
mintYesThe Solana token mint address to inspect for bundled buys.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / mint / description
      Added value: +"The Solana token mint address to inspect for bundled buys."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "detect_bundlesDictOutput",
+  "type": "object"
+}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the rest and does so well: it discloses the detection method, the confidence-scored output with its evidence (matching fees, block index, adjacency), and the Solana/Jito scope limit. It doesn't mention latency, rate limits, or coverage caveats (e.g., tokens with no Jito bundles).

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 and routing guidance are front-loaded and the paragraph is tight overall. Minor redundancy: the Solana-only constraint is stated twice ('Solana only, because it depends on Jito bundles') and the mint line duplicates the schema.

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 an output schema present, the description needn't enumerate return fields, yet it still summarizes what comes back (bundle, confidence, evidence). Purpose, scope, and trigger conditions are all covered for a one-parameter read-only 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?

Schema description coverage is 100% and the schema already documents the single 'mint' parameter identically. The trailing 'mint: the Solana token mint address' line merely restates it, adding no format or syntax detail beyond the schema.

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 (check/detect) and resource (KOL wallets buying a Solana token via Jito bundles with side wallets), plus the consequence it uncovers (hidden position size). No sibling tool covers bundle detection, so the agent can distinguish it immediately.

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?

Explicitly names the triggering user questions (bundled launch, insider-heavy, sniped, manipulated) and states a hard applicability constraint (Solana only, due to the Jito dependency). It stops short of naming alternatives or when-not-to-use, but the sibling set has no overlapping tool, so this is close to complete.

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

All wallet-tracker 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