Skip to main content
Glama

SolGuard Solana Token-2022 Scanner & Safe-Swap Router

Build Unsigned Post-Unwrap Jito Safe-Exit

build_jito_safe_exit
Read-only

Emergency Dump / Safe-Exit (Token -> SOL): builds an unsigned Solana v0 VersionedTransaction via Jupiter v1 + Jito bundleOnly=true MEV protection, APPENDING the 65 bps (or 45/20 bps partner referral) atomic SOL fee AFTER Jupiter unwraps WSOL so wallets with near-zero free SOL pay the fee directly out of SOL sale proceeds.

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": {
      "userPublicKey": "<userPublicKey>"
    },
    "name": "build_jito_safe_exit"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNoAlias for inputMint (token mint to exit into SOL)
sellPctNoPercentage of wallet ATA balance to dump (1-100, default 100)
amountRawNoOptional exact integer raw base units to sell instead of sellPct
inputMintNoToken mint Base58 address to sell into native SOL
slippageBpsNoMax slippage in basis points (10 to 3000, default 150)
amountTokensNoOptional exact UI token amount to sell instead of sellPct
userPublicKeyYesUser Solana wallet Base58 public key (fee payer & signer)
referrerPubkeyNoOptional partner Solana wallet Base58 pubkey for atomic 45/20 bps revenue split (earns 20 bps)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that: the tool builds an unsigned transaction rather than executing anything. Beyond the annotations it adds genuinely useful substance: Jito bundleOnly MEV protection, the 65 bps fee (45/20 bps with a referral), and the critical ordering detail that the fee is appended AFTER Jupiter unwraps WSOL so it is paid from sale proceeds.

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

Conciseness4/5

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

It is a single front-loaded sentence that opens with the use case and artifact before the mechanics, with no filler. It is dense with nested parentheses ('65 bps (or 45/20 bps partner referral)'), which slows parsing slightly, but every clause carries information.

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

Completeness4/5

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

With 8 parameters but one required and full schema coverage, the description only needs to explain the non-obvious mechanics, which it does well through the fee-after-unwrap and MEV-protection details. Since there is no output schema, it could say more about the returned payload (e.g., serialized base64 transaction awaiting signature), which is the main remaining gap.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented in-schema, including referrerPubkey's 'earns 20 bps' note. The description adds the surrounding fee economics (65 bps base vs 45/20 partner split, paid after unwrap), which gives context for the referral parameter but no new syntax or format guidance. Baseline 3 is appropriate.

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 names a specific verb and artifact: 'builds an unsigned Solana v0 VersionedTransaction' and scopes it as a Token -> SOL exit routed through Jupiter v1 with Jito bundleOnly. That scope implicitly separates it from the sibling build_jito_safe_swap, but the sibling is never named, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

'Emergency Dump / Safe-Exit' implies the scenario (urgent liquidation of a token position to SOL), and the note about wallets with near-zero free SOL explains one motivating condition. However, there is no explicit statement of when to prefer this over build_jito_safe_swap or a plain swap, and no prerequisites or exclusions are listed.

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