Skip to main content
Glama

cluster_check

Read-onlyIdempotent

Full cluster & consensus report for ONE token (Solana mint or Base contract address; chain auto-detected). Detects whether tracked smart-money wallets are converging on the token in the last 24h: tracked buyer/seller counts, per-wallet cluster events (side, tx count, estimated USD, first/last seen), tracked net USD flow, tracked wallets sitting in the top-holder list, and a 0-100 consensus score with a STRONG / FORMING / QUIET / EXITING signal and a stated confidence. Fuses a safety summary (RugCheck on Solana, GoPlus on Base) and a canonical check: for tokens trading on a registered narrative name (NEET at launch) it states CANONICAL or CLONE and names the real contract — ticker copies are industrial-scale and resolving the real one is the toll. FAIL-CLOSED AND HONEST ABOUT COVERAGE: Solana cluster detection is sample-based (a bounded sample of recent main-pool transactions intersected with the tracked set); every report states signatures seen, transactions parsed and the sample span, and missing sources cap confidence and are named in data_gaps — a consensus score is only produced when real cluster data answered. Base support is holder-overlap plus a bounded transfer-log scan and is labelled a weaker signal. The tracked set is derived from public data (repeat cross-token buyers on public RPC flow + GoPlus holder lists), shipped as data and rebuildable. Cost: $0.02 USDC per call via x402 (Base settlement; Solana settlement when configured) — no API key needed. Use it before apeing into any social-driven token: are the wallets that matter already in, still entering, or leaving?

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "cluster_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesToken address: a Solana mint (base58, e.g. Ce2gx9KGXJ6C9Mp5b5x1sn9Mg87JwEbrQby4Zqo3pump) or a Base contract (0x-prefixed, 40 hex chars). Chain is auto-detected from the format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile, and the description adds substantial context they cannot: $0.02 USDC cost via x402 with no API key, fail-closed scoring, sample-based Solana coverage with signatures/transactions/span disclosed, named data_gaps capping confidence, and explicit labeling of Base as a weaker signal. This is exactly the operational and reliability context an agent needs before spending money on a call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and return contents, which is good, but it is a dense wall of prose with all-caps emphasis and marketing flourishes ('ticker copies are industrial-scale and resolving the real one is the toll') that do not help an agent decide or invoke. Several sentences earn their place; the rhetorical ones do not.

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 no output schema, the description carries the full burden and does so: it enumerates every returned field group, the signal vocabulary, confidence, safety-source fusion, canonical-vs-clone result, and explicit coverage limits per chain. An agent knows what it will get and what the caveats are before calling.

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 coverage is 100% for the single parameter and its description already explains Solana mint vs Base 0x address formats and auto-detection. The description repeats chain auto-detection but adds no format, validation, or edge-case detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Full cluster & consensus report for ONE token') and enumerates the exact contents: buyer/seller counts, per-wallet cluster events, net flow, top-holder overlap, and a 0-100 consensus score with signal tiers. Differentiation from the lite sibling is only implied by the word 'Full' rather than named, so it falls short of a 5.

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 closing sentence gives concrete when-to-use guidance ('before apeing into any social-driven token') framed as a decision question about whether tracked wallets are in, entering, or leaving. It does not name an alternative or state when to prefer cluster_check_lite or cluster_feed, and gives no explicit exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.