Skip to main content
Glama
Sign In
MCP Helius

MCP Helius

by dcSpark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

helius_send_jito_bundle

Submit serialized transactions as a bundle to Jito for prioritized processing on Solana.

Instructions

Send a bundle of transactions to Jito

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": {
      "serializedTransactions": "<serializedTransactions>",
      "jitoApiUrl": "<jitoApiUrl>"
    },
    "name": "helius_send_jito_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
serializedTransactionsYes
jitoApiUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior1/5

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

No annotations provided. Description lacks any disclosure about side effects, permissions, rate limits, or return behavior. 'Send a bundle' implies mutation but no further transparency.

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?

Single sentence is concise but at the expense of essential detail. Not well structured for quick comprehension.

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

Completeness1/5

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

No output schema and minimal description. Tool performs a critical network operation (sending bundles) but omits return values, error handling, or confirmation behavior.

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?

Schema coverage is 0% and description adds no meaning to parameters. 'serializedTransactions' and 'jitoApiUrl' are undefined, leaving the agent to guess format and purpose.

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?

Description clearly states the action (send) and target (bundle to Jito). It distinguishes from most sibling tools which are get operations, but doesn't differentiate from other submission tools like Jupiter swap.

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 like helius_execute_jupiter_swap or other send endpoints. No context on prerequisites or typical use cases.

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

Deploy Server

Other Tools