Skip to main content
Glama

My MCP Server

jito-bundle-dispatcher

Live Solana Mainnet jito-bundle-dispatcher ($0.10 USDC via x402 v2 PAYMENT-SIGNATURE header)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jito-bundle-dispatcher"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one genuinely useful behavioral fact – a $0.10 USDC charge via an x402 v2 PAYMENT-SIGNATURE header, implying a payment prerequisite – but says nothing about irreversibility, mainnet-commit consequences, failure modes, or rate limits for a tool that submits live transactions.

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?

It is a single short fragment with no wasted preamble, so length is fine. However it is a parenthetical dump of network and pricing rather than a front-loaded statement of function, which makes it terse without being informative.

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?

For a paid tool that dispatches live mainnet transactions with two fully undocumented parameters and no output schema, the definition is far too thin – it never explains the request/response shape or what happens on payment failure. The pricing and header detail is the only completeness it offers.

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 description coverage is 0% and both properties ('mint', 'targetWallet') are undocumented in the schema. The description provides no meaning for either parameter, not even which token the bundle is built around or whose wallet receives the action, so an agent is left guessing at invocation syntax.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text names the tool and asserts 'Live Solana Mainnet,' but never states in a verb+resource form what the tool actually does (dispatch a Jito bundle of what, to where, for what outcome). An agent must infer the purpose from the hyphenated name itself, which is essentially a restatement rather than an explanation.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no conditions, and no mention of the closely related 'multi-wallet-jito-injector' sibling that an agent would need to disambiguate against. Nothing indicates under what circumstances bundle dispatch is preferred over the other transaction tools in the catalog.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources