Skip to main content
Glama

helius_send_jito_bundle

Send bundled transactions to Jito for processing on the Solana blockchain using the Helius API.

Instructions

Send a bundle of transactions to Jito

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serializedTransactionsYes
jitoApiUrlYes

Implementation Reference

  • The main handler function that executes the tool logic by calling the Helius RPC method to send a Jito bundle.
    export const sendJitoBundleHandler = async (input: SendJitoBundleInput): Promise<ToolResultSchema> => {
      try {
        const bundleId = await (helius as any as Helius).rpc.sendJitoBundle(input.serializedTransactions, input.jitoApiUrl);
        return createSuccessResponse(`Jito bundle sent: ${bundleId}`);
      } catch (error) {
        return createErrorResponse(`Error sending Jito bundle: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Input schema definition for the helius_send_jito_bundle tool, specifying serializedTransactions and jitoApiUrl.
    {
      name: 'helius_send_jito_bundle',
      description: 'Send a bundle of transactions to Jito',
      inputSchema: {
        type: 'object',
        properties: {
          serializedTransactions: { type: 'array', items: { type: 'string' } },
          jitoApiUrl: { type: 'string' }
        },
        required: ['serializedTransactions', 'jitoApiUrl']
      }
    },
  • src/tools.ts:587-587 (registration)
    Registration of the sendJitoBundleHandler in the global handlers dictionary.
    "helius_send_jito_bundle": helius.sendJitoBundleHandler,
  • TypeScript type definition for the input parameters used by the handler.
    export type SendJitoBundleInput = {
      serializedTransactions: string[];
      jitoApiUrl: string;
    }
Behavior2/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 states the tool sends transactions but lacks critical details: it doesn't specify if this is a read-only or destructive operation, what permissions or authentication are required, potential rate limits, or what happens upon sending (e.g., confirmation status, errors). This leaves significant gaps for an AI agent to understand the tool's behavior.

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, direct sentence with zero waste—it efficiently conveys the core action without unnecessary details. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 complexity of sending transactions (a potentially destructive operation), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't address key contextual aspects like error handling, return values, or behavioral traits, leaving the AI agent with insufficient information to use the tool effectively.

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?

The schema description coverage is 0%, meaning the input schema provides no descriptions for the two required parameters. The description does not add any meaning beyond the parameter names: it doesn't explain what 'serializedTransactions' or 'jitoApiUrl' are, their formats, or examples. This fails to compensate for the lack of schema documentation.

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 action ('Send a bundle of transactions') and the target ('to Jito'), which is a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'helius_execute_jupiter_swap' or 'helius_get_bundle_statuses', which might handle similar transaction-related operations but with different purposes.

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, such as needing serialized transactions or a Jito API URL, nor does it explain why one would choose this over other transaction-related tools like 'helius_execute_jupiter_swap' or 'helius_get_bundle_statuses'.

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