Skip to main content
Glama

Solana Rent & Rug Shield MCP Gateway

Read-Only Solana Wallet Unclaimed ATA & Token-2022 SOL Rent Scanner

scan_wallet_unclaimed_sol
Read-onlyIdempotent

Read-only Solana wallet ATA and Token-2022 rent scanner. Identifies empty and dust token accounts holding reclaimable SOL rent without requiring private keys, returning exact lamport, SOL, and USD recovery breakdowns.

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": {
      "wallet": "<wallet>"
    },
    "name": "scan_wallet_unclaimed_sol"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesSolana wallet public key (base58) to scan read-only for reclaimable ATA rent.
x_paymentNoOptional base64 or JSON Solana x402 payment payload (X-Payment / PAYMENT-SIGNATURE) for automatic HTTP 402 settlement.
pro_pass_tokenNoOptional X-Pro-Pass-Token from Option A Unlimited Pro Pass.
payment_signatureNoOptional confirmed Solana transaction signature paying 89Sv5FvnMNRid1bn8y2Ti1vJPSxWxgiW9GSLsPpBnKK1 for x402 retry.
include_token_2022NoInclude Token-2022 accounts alongside SPL Token accounts (default: true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value by disclosing the no-private-key property and the lamport/SOL/USD recovery breakdown, but it omits the payment/402 settlement behavior implied by x_payment, pro_pass_token and payment_signature, which an agent could hit unexpectedly.

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?

Two sentences, front-loaded with the read-only scan scope and followed by the concrete value proposition. Dense but every clause carries information; only minor jargon stacking ('ATA and Token-2022 rent') costs a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter tool with no output schema, the description covers purpose and output shape well enough. The significant gap is the unmentioned payment/settlement workflow behind three optional parameters and the x402 402-response path, which an agent needs in order to invoke this successfully.

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 every parameter including the payment fields is already documented in the schema. The description adds no parameter-level meaning (no default behavior for include_token_2022, no guidance on when payment fields are needed), 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: a read-only scan of a Solana wallet's ATA and Token-2022 accounts for reclaimable SOL rent, naming the exact object of interest (empty and dust token accounts). It is clearly distinct from a token audit or a transaction simulation, though it never explicitly differentiates itself from the listed siblings.

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?

Usage is implied by the purpose: call it when you want to discover reclaimable rent on a wallet. It adds one useful qualifying note ('without requiring private keys') but provides no when-not guidance, no prerequisites, and no mention of the paid/x402 path implied by three of the five parameters.

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.