Skip to main content
Glama

arcanumfleet-mcp-server

ArcanumFleet Solana Wallet Portfolio & Profiler

arcanum_wallet_profile
Read-onlyIdempotent

Use this to inspect any Solana wallet's live SOL balance, top SPL token holdings, recent tx activity, and whale/trader tier — 0 API keys. Costs 0.003 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": {
      "address": "<address>"
    },
    "name": "arcanum_wallet_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesSolana wallet public key (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds genuinely non-redundant behavior: no API keys are required, and the call is metered at 0.003 USDC via x402 — critical pre-invocation context for an agent paying per call. It omits any statement about rate limits, data freshness, or how many "top" tokens or "recent" transactions are returned.

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?

One front-loaded sentence names the use case first, then the concrete outputs, then the cost/credential constraints. No filler, no repetition of the title, and nothing an agent must skip past to find the trigger.

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 one-parameter read-only tool with full schema coverage and explicit annotations and no output schema, the description covers purpose, trigger, and payment/auth prerequisites. The remaining gaps — how many holdings or transactions constitute "top"/"recent" and error behavior on bad keys — are minor.

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% and the single address parameter is already documented as a base58 Solana public key. The description only implies "any wallet" scope and adds no format, validation, or edge-case detail (e.g., behavior for an invalid or non-existent key), 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?

The description gives a specific verb (inspect) and resource (any Solana wallet) and enumerates the concrete outputs: live SOL balance, top SPL token holdings, recent tx activity, and whale/trader tier. This clearly separates it from siblings like arcanum_liquidity_check or arcanum_audit, though it never names or contrasts an alternative 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 any Solana wallet's..." supplies a positive trigger condition, which is more than nothing. However, there is no guidance on when not to use it and no routing to sibling profiler/activity tools, so the agent must infer the boundary itself.

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.