Skip to main content
Glama

Yield-Bearing RWA Treasury & 2-Second Cross-Chain Bridge MCP

Build MEV-Protected & Sandwich-Shielded Swap Calldata (Flashbots / Private Sequencer)

build_mev_protected_flashbots_swap
Read-onlyIdempotent

Pairs non-custodial volume-tiered swap calldata with private Flashbots Protect / MEV-Blocker / L2 Sequencer RPC routing so trading agents avoid 1%-3% public mempool sandwich attacks. Includes interactive MCP App UI.

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": "build_mev_protected_flashbots_swap"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNoHuman-readable input amount (default 250)
senderNoOptional 0x wallet address
chainIdNoEVM chain ID ('1' Ethereum Flashbots/MEV-Blocker, '8453' Base, '42161' Arbitrum, '137' Polygon)
srcSymbolNoSell token symbol ('USDC' or 'ETH')
destTargetNoBuy token symbol ('WETH', 'SUSDS', 'USDC') or 0x contract

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the non-mutating profile is covered structurally. The description adds useful context beyond that - non-custodial, private-RPC routing, and an interactive MCP App UI that changes the response shape - but it never states whether the tool merely returns calldata or broadcasts anything, nor what the caller does with the output.

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?

Two sentences, front-loaded with the core verb and mechanism, and the second sentence carries actionable information about the bundled UI rather than filler. Slightly dense marketing phrasing ('volume-tiered', 'sandwich-shielded') costs some clarity but not much length.

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 non-required-parameter calldata builder with no output schema, the description should say what comes back and how to use it; it only gestures at 'pairs ... calldata with ... routing'. Combined with the 100%-covered schema and safety annotations the tool is callable, but the return contract and the absence of execution are left for the agent to guess.

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%, with chain IDs, token symbols and the default amount all documented inline, so the baseline of 3 applies. The description adds no parameter meaning beyond the schema - it does not mention defaults, symbol-to-contract resolution, or what destTarget's 0x-contract form implies for routing.

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 concrete artifact (swap calldata) plus a delivery mechanism (private Flashbots Protect / MEV-Blocker / L2 sequencer RPC routing) and a rationale (avoiding mempool sandwich attacks), so the agent knows this is a calldata builder rather than a quote or execution tool. It is weakened by promotional framing ('non-custodial volume-tiered', '1%-3%') and never names the obvious sibling build_smart_dex_swap_calldata as the unprotected alternative.

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?

Use intent is only implied: an agent can infer this is for swaps needing sandwich protection, but there is no explicit when-to-use versus quote_low_fee_dex_swap or build_smart_dex_swap_calldata, and no when-not guidance. Nothing is misleading, but the routing decision between siblings is left to inference.

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.