Skip to main content
Glama
Sign In

SealGuard

by io.github.2cstudiodev-web
OverviewDiscussionsAdmin

List empty token accounts and the SOL in them

list_empty_token_accounts
Read-only

Lists a Solana wallet's empty token accounts (left behind by sold or sent tokens), the SOL rent locked in each, and which ones SealGuard suggests closing. Accounts for tokens the owner will likely receive again, or used in the last 30 days, are marked to keep, with the reason. Also lists pump.fun and PumpSwap deposits the wallet can take back. Read-only; returns a link where the owner can close them.

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

Input Schema

NameRequiredDescriptionDefault
addressYesThe Solana wallet address (base58 public key) to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context beyond them: the keep/close heuristic (tokens likely received again, or used in the last 30 days, with reasons), the inclusion of pump.fun/PumpSwap deposits, and the fact that it returns a link for closing. It does not detail rate limits or the exact response shape, but the behavioral picture is substantially richer than the annotations alone.

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?

Three sentences, front-loaded with the core action and followed by the keep/close logic and the read-only/link note. Dense but every clause carries information; no filler.

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, no-output-schema read tool, the description covers what is returned (accounts, rent amounts, suggestions with reasons, reclaimable deposits, a closing link) and the safety profile. Only minor gaps remain, such as the exact response structure or pagination behavior.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains the base58 wallet address. The description adds no format or constraint detail beyond that, which is the expected baseline when the schema does the work.

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 names a specific verb and resource: listing a Solana wallet's empty token accounts, the SOL rent locked in each, and SealGuard's close/keep suggestions. It also covers pump.fun and PumpSwap deposits, so the scope is concrete. It does not explicitly differentiate itself from siblings like list_token_approvals or scan_wallet, which keeps it at 4 rather than 5.

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 scenario described (accounts left behind by sold or sent tokens, rent to reclaim), but there is no explicit when-to-use or when-not guidance and no named alternative. An agent can infer the purpose but must decide on its own when this beats scan_wallet.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SealGuard toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources