Skip to main content
Glama

Solana wallet risk scan (free summary)

scan_wallet
Read-only

Read-only Solana wallet scan: every SPL / Token-2022 token held with its Rugsight grade and flags (top 20 by USD value), active delegate approvals, empty token accounts with reclaimable rent, and possible address-poisoning lookalikes from recent transactions. Automated technical data, not financial advice. Returns the free summary (counts, grade distribution, top 5 graded tokens); limited to 3 calls per day per IP. The full per-token JSON is GET /api/wallet-scan/?full=1 for 0.01 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": "scan_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesSolana wallet address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavior: top-20-by-USD-value token coverage, exact summary contents, rate limiting, pricing for the full endpoint, and a clear non-advice disclaimer. This gives the agent enough context to invoke it correctly and understand what data is and is not included.

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?

The description is front-loaded with the scan scope and then covers return shape, limits, and the paid alternative. It is dense but every sentence contributes relevant information, with no obvious filler.

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?

For a one-parameter read-only scan with no output schema, the description explains what is scanned, what the free summary contains, the rate limit, and where to obtain full per-token JSON. Nothing essential for correct invocation 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% and the single address parameter is already fully documented as a base58 Solana wallet address. The description adds no extra parameter-level format or validation details beyond the schema, so the baseline score of 3 is appropriate.

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: a read-only Solana wallet scan. It enumerates the exact data returned, including SPL/Token-2022 holdings, delegate approvals, empty token accounts, and address-poisoning lookalikes, which clearly distinguishes it from token-level sibling tools.

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 description clearly frames this as the free summary path and names the paid full per-token endpoint as the alternative when detailed JSON is needed. It also states the 3-calls-per-day limit, though it does not explicitly compare usage against the token risk report/score siblings.

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