Skip to main content
Glama

My MCP Server

multi-wallet-jito-injector

Live Solana Mainnet multi-wallet-jito-injector ($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": "multi-wallet-jito-injector"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: it operates on live mainnet (real funds, irreversible effects) and requires a $0.10 USDC payment via an x402 v2 PAYMENT-SIGNATURE header — auth/payment mechanics an agent otherwise could not guess. However, it says nothing about what the tool actually does to wallets or transactions, whether it signs/sends on the caller's behalf, failure modes, or idempotency.

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

Conciseness2/5

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

It is short and front-loaded, but that brevity is under-specification rather than concision: a one-line parenthetical price note is the only non-name content, and the essential action is absent.

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 a live-mainnet, paid, mutating tool with zero annotation coverage, no output schema, and 0% parameter documentation, the description should clarify the operation and the two inputs. It supplies only the payment mechanism, leaving the agent unable to invoke the tool correctly with confidence.

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 there are two undocumented parameters (mint, targetWallet), yet the description mentions neither. It does not explain the format of mint, how targetWallet relates to "multi-wallet", or which are required (required list is empty), so nothing compensates for the schema gap.

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 description largely restates the name ("multi-wallet-jito-injector") and adds only the network ("Live Solana Mainnet") and a price. The key verb/object is never defined: what is being "injected" (a bundle? a swap? a transaction?) is left entirely to inference, so an agent cannot tell this apart from sibling jito-bundle-dispatcher or mev-arbitrage-bot.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative. The only actionable hint is the implied pay-per-call cost, which does not indicate the scenario this tool serves.

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