Skip to main content
Glama

helius_get_bundle_statuses

Check the status of Jito bundles by providing bundle IDs and a Jito API URL.

Instructions

Get statuses of Jito bundles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bundleIdsYes
jitoApiUrlYes

Implementation Reference

  • The actual handler function that executes the get bundle statuses logic. Calls helius.rpc.getBundleStatuses with bundleIds and jitoApiUrl input parameters.
    export const getBundleStatusesHandler = async (input: GetBundleStatusesInput): Promise<ToolResultSchema> => {
      try {
        const statuses = await (helius as any as Helius).rpc.getBundleStatuses(input.bundleIds, input.jitoApiUrl);
        return createSuccessResponse(`Bundle statuses: ${JSON.stringify(statuses, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting bundle statuses: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • TypeScript type definition for the input schema of getBundleStatuses. Defines required fields: bundleIds (string array) and jitoApiUrl (string).
    export type GetBundleStatusesInput = {
      bundleIds: string[];
      jitoApiUrl: string;
    }
  • src/tools.ts:549-592 (registration)
    Registration of the handler in the handlers dictionary, mapping the tool name 'helius_get_bundle_statuses' to the function helius.getBundleStatusesHandler (imported as getBundleStatusesHandler at line 27).
    export const handlers: handlerDictionary = {
      "helius_get_balance": getBalanceHandler,
      "helius_get_block_height": getBlockHeightHandler,
      "helius_get_token_accounts_by_owner": getTokenAccountsByOwnerHandler,
      "helius_get_token_supply": getTokenSupplyHandler,
      "helius_get_token_largest_accounts": getTokenLargestAccountsHandler,
      "helius_get_latest_blockhash": getLatestBlockhashHandler,
      "helius_get_token_account_balance": getTokenAccountBalanceHandler,
      "helius_get_slot": getSlotHandler,
      "helius_get_transaction": getTransactionHandler,
      // New handlers
      "helius_get_account_info": getAccountInfoHandler,
      "helius_get_program_accounts": getProgramAccountsHandler,
      "helius_get_signatures_for_address": getSignaturesForAddressHandler,
      "helius_get_minimum_balance_for_rent_exemption": getMinimumBalanceForRentExemptionHandler,
      "helius_get_multiple_accounts": getMultipleAccountsHandler,
      "helius_get_inflation_reward": getInflationRewardHandler,
      "helius_get_epoch_info": getEpochInfoHandler,
      "helius_get_epoch_schedule": getEpochScheduleHandler,
      "helius_get_leader_schedule": getLeaderScheduleHandler,
      "helius_get_recent_performance_samples": getRecentPerformanceSamplesHandler,
      "helius_get_version": getVersionHandler,
      // DAS Methods
      "helius_get_asset": helius.getAssetHandler,
      "helius_get_rwa_asset": helius.getRwaAssetHandler,
      "helius_get_asset_batch": helius.getAssetBatchHandler,
      "helius_get_asset_proof": helius.getAssetProofHandler,
      "helius_get_assets_by_group": helius.getAssetsByGroupHandler,
      "helius_get_assets_by_owner": helius.getAssetsByOwnerHandler,
      "helius_get_assets_by_creator": helius.getAssetsByCreatorHandler,
      "helius_get_assets_by_authority": helius.getAssetsByAuthorityHandler,
      "helius_search_assets": helius.searchAssetsHandler,
      "helius_get_signatures_for_asset": helius.getSignaturesForAssetHandler,
      "helius_get_nft_editions": helius.getNftEditionsHandler,
      "helius_get_token_accounts": helius.getTokenAccountsHandler,
      // Transaction and Fee Methods
      "helius_get_priority_fee_estimate": helius.getPriorityFeeEstimateHandler,
      "helius_poll_transaction_confirmation": helius.pollTransactionConfirmationHandler,
      "helius_send_jito_bundle": helius.sendJitoBundleHandler,
      "helius_get_bundle_statuses": helius.getBundleStatusesHandler,
      "helius_get_fee_for_message": getFeeForMessageHandler,
      "helius_execute_jupiter_swap": executeJupiterSwapHandler
      // "print_environment": printEnvironmentHandler,
    }
  • src/tools.ts:492-503 (registration)
    Tool definition/registration in the tools array. Includes name, description, and inputSchema for the tool.
    {
      name: 'helius_get_bundle_statuses',
      description: 'Get statuses of Jito bundles',
      inputSchema: {
        type: 'object',
        properties: {
          bundleIds: { type: 'array', items: { type: 'string' } },
          jitoApiUrl: { type: 'string' }
        },
        required: ['bundleIds', 'jitoApiUrl']
      }
    },
Behavior2/5

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

The description does not disclose any behavioral traits such as whether the tool requires authentication, rate limits, or what happens to the data queried. Without annotations, the description should provide more context but fails to do so.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (3 words), which is concise but at the expense of clarity. It does not waste words but is under-informative for a tool with two parameters.

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 the lack of annotations, output schema, and parameter descriptions, the description is incomplete. It does not explain what bundle statuses are returned, how to construct the jitoApiUrl, or what the response looks like.

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

Parameters1/5

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

The input schema has 0% schema description coverage, and the description does not explain the purpose or format of the parameters (bundleIds, jitoApiUrl). No additional meaning is provided beyond the parameter names.

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 'Get statuses of Jito bundles' clearly states the verb (Get) and resource (statuses of Jito bundles). It distinguishes from sibling tools like helius_send_jito_bundle, but lacks specificity on what kind of statuses are returned.

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?

No guidance on when to use this tool versus alternatives. It does not mention that it should be used after sending a bundle via helius_send_jito_bundle, nor does it provide any contextual cues for usage.

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