Skip to main content
Glama
solclaimer

SOL Claimer MCP Server

by solclaimer

analyze_burnable_accounts

Analyze Solana wallets to identify token accounts with minimal value that can be burned to recover SOL rent. Provides token details and USD values for each account.

Instructions

Analyze a Solana wallet for token accounts with balances worth less than $1 USD that can be burned and closed. Returns detailed information about each burnable account including token name, symbol, and USD value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_addressYesThe Solana wallet address to analyze

Implementation Reference

  • The main handler that processes the analyze_burnable_accounts tool call. It extracts the wallet_address argument, validates it, calls the API client method, and returns the formatted response.
    } else if (name === "analyze_burnable_accounts") {
      const walletAddress = (args as Record<string, string>).wallet_address;
      if (!walletAddress) {
        throw new Error("wallet_address is required");
      }
    
      const result = await apiClient.analyzeBurnableAccounts(walletAddress);
      return {
        content: [
          {
            type: "text",
            text: formatBurnableAccountsResponse(result),
          },
        ],
      };
  • src/index.ts:157-171 (registration)
    Tool registration defining the analyze_burnable_accounts tool with its name, description, and inputSchema that requires a wallet_address parameter.
      name: "analyze_burnable_accounts",
      description:
        "Analyze a Solana wallet for token accounts with balances worth less than $1 USD that can be burned and closed. " +
        "Returns detailed information about each burnable account including token name, symbol, and USD value.",
      inputSchema: {
        type: "object" as const,
        properties: {
          wallet_address: {
            type: "string",
            description: "The Solana wallet address to analyze",
          },
        },
        required: ["wallet_address"],
      },
    },
  • The SolClaimerApiClient.analyzeBurnableAccounts method that makes the actual HTTP POST request to the backend API endpoint '/api/v1/accounts/analyze-burnable'.
    async analyzeBurnableAccounts(walletAddress: string): Promise<BurnableAccountsAnalysis> {
      try {
        const response = await this.apiClient.post<BurnableAccountsAnalysis>(
          "/api/v1/accounts/analyze-burnable",
          { walletAddress }
        );
        return response.data;
      } catch (error) {
        throw new Error(
          `Failed to analyze burnable accounts: ${
            error instanceof Error ? error.message : "Unknown error"
          }`
        );
      }
    }
  • TypeScript interface BurnableAccountsAnalysis defining the response structure including accountsToBurn, totalSol, totalUsdValue, and accountDetails array.
    interface BurnableAccountsAnalysis {
      success: boolean;
      data: {
        accountsToBurn: number;
        totalSol: number;
        totalUsdValue: number;
        accountDetails: AccountDetail[];
      };
      timestamp: string;
    }
  • The formatBurnableAccountsResponse helper function that formats the API response into a human-readable string with account details including token name, amount, USD value, and verification status.
    function formatBurnableAccountsResponse(data: BurnableAccountsAnalysis): string {
      if (!data.success) {
        return "Failed to analyze burnable accounts";
      }
    
      let response = `
    Burnable Token Accounts Analysis
    =================================
    Total Accounts to Burn: ${data.data.accountsToBurn}
    Total SOL to Recover: ${data.data.totalSol} SOL
    Total USD Value: $${data.data.totalUsdValue.toFixed(2)}
    
    Accounts Details:
    `;
    
      data.data.accountDetails.forEach((account, index) => {
        response += `
    ${index + 1}. ${account.tokenName} (${account.tokenSymbol})
       Mint: ${account.mint}
       Amount: ${account.uiAmount} (${account.amount} smallest units)
       USD Value: $${account.usdValue.toFixed(2)}
       Lamports (rent): ${account.lamports}
       Verified Contract: ${account.isVerifiedContract ? "Yes" : "No"}
    `;
      });
    
      return response;
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the analysis function and return details, but does not cover critical aspects like permissions needed, rate limits, whether the tool performs actual burning/closing or just analysis, or error handling. It adds some value but leaves gaps in behavioral context.

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?

The description is a single, well-structured sentence that efficiently conveys the tool's purpose, criteria, and return information without any wasted words. It is front-loaded with the core action and appropriately sized for the tool's complexity.

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?

Given no annotations and no output schema, the description provides a basic overview but lacks completeness. It explains what the tool does and returns, but does not cover behavioral traits like safety, performance, or error cases. For a tool with no structured metadata, more detail on operations and outputs would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the input schema already documents the 'wallet_address' parameter. The description adds no additional parameter semantics beyond what the schema provides, but with only one parameter, the baseline is high. It does not compensate for any gaps, but the simplicity of parameters keeps the score above baseline.

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 clearly states the specific action ('analyze'), target resource ('Solana wallet for token accounts'), and precise criteria ('balances worth less than $1 USD that can be burned and closed'). It distinguishes from sibling tools like 'analyze_empty_accounts' by focusing on burnable accounts with minimal value rather than empty ones.

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?

The description implies usage when a user wants to identify and potentially close low-value token accounts, but it does not explicitly state when to use this tool versus alternatives like 'analyze_empty_accounts' or provide exclusions. The context is clear but lacks explicit guidance on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/solclaimer/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server