Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

agent_mev_shield_check

[$0.05] Evaluate swap or arbitrage MEV sandwich exposure, pool liquidity ratio, safe slippage bounds, and recommended private-RPC relay before signing.

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

Input Schema

NameRequiredDescriptionDefault
chainNoTarget chain ('base' or 'ethereum')base
calldataNoOptional hex calldata to inspect for router/deadline flags
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data
swap_value_usdNoNotional swap value in USD
slippage_tolerance_bpsNoCaller slippage tolerance in basis points

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?

With no annotations supplied, the description carries the full behavioral burden. It discloses the $0.05 price and, via "before signing" plus "recommended private-RPC relay," signals that this is an advisory pre-signature check rather than something that submits a transaction. It does not state side effects, whether any state is persisted, latency expectations, or auth requirements beyond what the timeout_ms schema implies.

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?

A single front-loaded sentence with the price tag up front and no filler. The dense four-item noun list is slightly packed but every clause maps to a capability the caller cares about. Nothing is wasted, though readability would improve if the outputs were separated from the trigger phrase.

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?

There is no output schema and no annotations, so the description is the only place an agent could learn the response shape, yet it never says what is actually returned (a risk score, a boolean safe/unsafe verdict, a relay URL, or a report object). For a paid, five-parameter advisory tool, that is a meaningful gap even though the inputs are fully covered by the schema.

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 the five parameters, their defaults, bounds, and the degraded-response behavior of timeout_ms are already documented in the schema. The description adds only loose mapping ("safe slippage bounds" to slippage_tolerance_bps, "pool liquidity ratio" as an output) and no format or interaction detail. Baseline 3 applies when the schema does the heavy lifting.

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 uses a specific verb ("Evaluate") applied to a concrete set of outputs: MEV sandwich exposure, pool liquidity ratio, slippage bounds, and a private-RPC relay recommendation, tied to swap/arbitrage transactions. An agent can tell this is an advisory MEV-risk check. It does not name or contrast itself with adjacent siblings such as agent_preflight, agent_execution_firewall, or security_preflight_402, so the differentiation is implicit 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?

"Before signing" gives a clear temporal trigger for calling the tool, which is useful usage context. However, there is no explicit statement of when NOT to use it, no mention of which sibling to use for gas sponsorship, arbitrage discovery, or general preflight, and no prerequisites. Usage is implied rather than prescribed.

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