Skip to main content
Glama

Flashbots MEV Shield, Polymarket CLOB Bridge & Kelly-Criterion MCP

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

build_mev_protected_flashbots_swap
Read-onlyIdempotent

Pairs non-custodial 0.25% swap calldata with private Flashbots Protect / MEV-Blocker / L2 Sequencer RPC routing so trading agents avoid 1%-3% public mempool sandwich attacks.

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

A3.6/5.0
Behavior3/5

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

The description adds real context beyond the annotations: 0.25% fee, non-custodial, private relay routing, and the threat model being defended against. It does not resolve the key behavioral question of whether the tool only returns calldata to submit or actually routes/submits the transaction, which matters given readOnlyHint=true. That ambiguity keeps it at a middling score despite the useful fee and routing detail.

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?

One dense sentence with no filler; fee, routing backends, and rationale are all front-loaded. The phrasing is marketing-flavored ('Pairs ... calldata with ... routing') rather than a clean verb-resource statement, which is the only structural weakness.

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

Completeness5/5

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

Placeholder.

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 coverage is 100% and each parameter already carries its own description including accepted chain IDs and token symbols. The description adds nothing about parameters (no default amount, no symbol constraints), so it sits at the baseline where the schema does all the work.

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 title and description make the resource concrete: swap calldata built for MEV-protected routing via Flashbots Protect / MEV-Blocker / L2 sequencer RPCs. That scope clearly separates it from the plain build_smart_dex_swap_calldata sibling even though the sibling is never named. The verb is slightly indirect ('pairs ... calldata with ... routing'), but the outcome is unambiguous.

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?

Usage is implied by the stated benefit ('so trading agents avoid 1%-3% public mempool sandwich attacks'), which tells an agent this is the choice when sandwich resistance matters. However, there is no explicit when-to-use/when-not guidance, no mention of which chains or private endpoints are supported for routing, and no contrast with the non-protected swap builder.

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.