Skip to main content
Glama

Scan a public Solana wallet

scan_wallet
Read-only

List the SPL tokens held by a PUBLIC Solana wallet address, riskiest first, with a quick risk score and top red flags per token. Never send a private key or seed phrase. Free: the 3 riskiest tokens, 5 scans/day per IP; Pro key: every token, unlimited. Automated risk signals, not financial advice. A low score is not a recommendation to buy.

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": "scan_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesPublic Solana wallet address (never a private key)
api_keyNoRugRadar Pro API key (optional; alternatively send Authorization: Bearer <key>).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and non-destructive, so the safety profile is covered. The description adds information annotations cannot carry: hard rate limits per IP, that the free tier silently truncates the result to the 3 riskiest tokens, that a Pro key is needed for full coverage, and the automated-signal / not-advice caveat. Return structure is still only sketched, which keeps it from a 5.

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?

Front-loaded with what the tool returns and in what order, followed by safety, tiering, and disclaimer. It is a bit dense with marketing/disclaimer phrasing ('Automated risk signals, not financial advice. A low score is not a recommendation to buy.'), but each sentence carries a constraint the caller needs.

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 two-parameter read tool with no output schema, the description covers input constraints, rate limits, tier-dependent result completeness, and a partial picture of the return shape (token list, risk score, red flags). Field-level return details are absent, but nothing essential to invoking it correctly is missing.

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%, so both 'address' and 'api_key' are already documented, including the public-key constraint and the Bearer alternative. The description adds only the contextual framing of the api_key as a Pro key that unlocks full results; that is useful but marginal against a fully documented schema, so baseline 3 applies.

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 states a specific verb and resource ('List the SPL tokens held by a PUBLIC Solana wallet address'), gives the ordering ('riskiest first') and the per-token payload ('quick risk score and top red flags'). That distinguishes it clearly from a single-token check or a link scan without the agent needing another schema.

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?

It establishes the preconditions for good use – public address only, never a private key – and explains the free vs Pro tiers (3 riskiest tokens, 5 scans/day per IP vs every token unlimited), which directly informs which call the agent can make. It stops short of explicitly routing the agent to a sibling such as check_token for single-token lookups.

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.