Risk
Risk primitives answer protocol-specific exposure questions that don’t generalize across AMM families. The category fans out by design — what “risk” means differs structurally per AMM (range-status for V3, depeg for Stableswap, weight-imbalance for Balancer, MEV/slippage for V2 — handled in Execution).
Primitives in this category
Section titled “Primitives in this category”CheckTickRangeStatus— V3-only. “Is my range still active?”AssessDepegRisk— Stableswap-only. Closed-form ε ↔ δ depeg-risk surface across N magnitudes.
Protocol coverage
Section titled “Protocol coverage”Risk is the most protocol-divergent category in v2.0. Forcing the questions into a single primitive would conflate three structurally different concerns.
| Protocol | Coverage | Notes |
|---|---|---|
| Uniswap V2 | N/A | V2’s symmetric reserves don’t have V3’s range-status risk or Stableswap’s depeg risk; V2-specific risks (MEV, slippage) live in Execution. |
| Uniswap V3 | Full | CheckTickRangeStatus answers the dominant V3-specific position risk. |
| Balancer | Deferred (v2.1) | Weight-imbalance and out-of-band swap-fee risks tracked but not yet primitive-formalized. |
| Stableswap | Full | AssessDepegRisk via the closed-form ε ↔ δ derivation; 2-asset only in v1. |
MCP tool exposure
Section titled “MCP tool exposure”In the curated v2.0 set: AssessDepegRisk. Not in: CheckTickRangeStatus (high-traffic V3 question but easy to compose LLM-side from lp.slot0.tick and the position’s saved lwr_tick/upr_tick).