Skip to main content
Glama

ArcanumFleet Smart Money & Holder Check

arcanum_smart_money
Read-onlyIdempotent

Use this to inspect top-10 holder concentration, insider network count, and mint/freeze authority revocation for a Solana mint via RugCheck. Costs 0.005 USDC via x402.

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": {
      "mint": "<mint>"
    },
    "name": "arcanum_smart_money"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesBase58 Solana SPL token mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mint / description
      Previous value: -"Solana token mint address"New value: +"Base58 Solana SPL token mint address"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior, so the description's main added value is disclosing that the call costs 0.005 USDC via x402 and depends on a third-party source (RugCheck). That payment/auth context is exactly the kind of detail annotations cannot convey. It stops short of describing failure modes or what happens if payment or RugCheck lookup fails.

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?

Two tight sentences: the first front-loads the action and the three metrics, the second carries the cost constraint. No filler or repetition, and the most decision-relevant information (what you get) leads.

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?

For a single-parameter read tool with no output schema, the enumerated metrics act as an implicit description of the returned fields, and the cost line covers the payment precondition. Only the response shape (e.g., score thresholds or pass/fail flags for authority revocation) is left unspecified.

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?

With one parameter at 100% schema coverage, the schema already explains that 'mint' is a Base58 SPL token mint address. The description only restates 'for a Solana mint' and adds no format, validation, or edge-case detail, 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 ('inspect') and enumerates the exact resources returned: top-10 holder concentration, insider network count, and mint/freeze authority revocation, scoped to a Solana mint and sourced via RugCheck. That metric list effectively separates it from siblings like arcanum_audit or arcanum_liquidity_check, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this to inspect...' gives an implied trigger (token due-diligence on a Solana mint), but there is no explicit when-not guidance, no prerequisites, and no routing to alternatives such as the audit or liquidity tools. The agent must infer the boundary between this and neighboring checks.

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.

Resources