Skip to main content
Glama

helius_get_minimum_balance_for_rent_exemption

Calculate the minimum SOL balance needed for rent exemption on Solana based on data size and commitment level.

Instructions

Get the minimum balance required for rent exemption

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataSizeYes
commitmentNo

Implementation Reference

  • The main handler function that executes the tool logic by calling the Helius connection's getMinimumBalanceForRentExemption method with the provided dataSize and commitment.
    export const getMinimumBalanceForRentExemptionHandler = async (input: GetMinimumBalanceForRentExemptionInput): Promise<ToolResultSchema> => {
      try {
        const minBalance = await (helius as any as Helius).connection.getMinimumBalanceForRentExemption(input.dataSize, input.commitment);
        return createSuccessResponse(`Minimum balance for rent exemption: ${minBalance}`);
      } catch (error) {
        return createErrorResponse(`Error getting minimum balance: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • The MCP tool definition including the input schema for validation of dataSize (required number) and optional commitment level.
    {
      name: "helius_get_minimum_balance_for_rent_exemption",
      description: "Get the minimum balance required for rent exemption",
      inputSchema: {
        type: "object",
        properties: {
          dataSize: { type: "number" },
          commitment: { type: "string", enum: ["confirmed", "finalized", "processed"] }
        },
        required: ["dataSize"]
      }
    },
  • src/tools.ts:563-563 (registration)
    Mapping of the tool name to its handler function in the central handlers dictionary used for tool execution.
    "helius_get_minimum_balance_for_rent_exemption": getMinimumBalanceForRentExemptionHandler,
  • TypeScript interface defining the input shape for the handler function, matching the MCP schema.
    export type GetMinimumBalanceForRentExemptionInput = {
      dataSize: number;
      commitment?: "confirmed" | "finalized" | "processed";
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states what the tool does but doesn't disclose: whether this is a read-only operation (implied but not explicit), potential rate limits, authentication requirements, error conditions, or what 'rent exemption' means in context. For a tool with zero annotation coverage, this is inadequate transparency.

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 maximally concise - a single sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple lookup tool and front-loads the core functionality immediately. Every word earns its place.

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

Completeness2/5

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

Given 2 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (just a number? structured data?), doesn't clarify parameter meanings, and provides no behavioral context. For a tool that calculates financial requirements, this leaves too many gaps for reliable agent usage.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but fails to do so. It mentions no parameters at all, leaving both 'dataSize' and 'commitment' completely unexplained. The agent cannot infer what 'dataSize' represents (bytes? account size?), what 'commitment' means in this context, or why one is required while the other isn't. This creates significant ambiguity for proper tool invocation.

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 clearly states the tool's purpose: 'Get the minimum balance required for rent exemption' - a specific verb ('Get') and resource ('minimum balance for rent exemption'). It distinguishes from obvious siblings like 'helius_get_balance' which retrieves actual balances rather than exemption requirements. However, it doesn't explicitly differentiate from all 30+ sibling tools, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing to know data size), use cases (e.g., account creation planning), or contrast with similar tools like 'helius_get_balance' or 'helius_get_fee_for_message' that might be relevant for cost calculations. The agent must infer usage from the name alone.

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/dcSpark/mcp-server-helius'

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