Never Let an LLM Guess Wellbore Pressures: Deterministic Physics as MCP Tools

Posted on Nov 5 • Originally published at eng.kcklayton.com

Originally published with interactive math formulas and diagrams at eng.kcklayton.com

Large Language Models (LLMs) are exceptional at synthesizing drilling logs, interpreting standard operating procedures (SOPs), and reasoning through complex operational triage.

However, in safety-critical operations—where bottomhole circulating pressures exceed $10,000\text{ psi}$ and kicking gas migrates at hundreds of feet per hour— an LLM must never be permitted to generate pressure values or kill mud calculations via token prediction.

Token generation is probabilistic. Well control physics must be deterministic.

If an autonomous rig agent hallucinates an Initial Circulating Pressure by just $80\text{ psi}$, it can collapse the casing or fracture the formation, escalating an ordinary kick into a surface blowout.

To harness the cognitive and reasoning capabilities of AI agents without risking physical hallucinations, we pair agentic reasoning frameworks with deterministic engineering engines via the Model Context Protocol (MCP).

flowchart LR A[Rig Stream / WITSML] --> B[AI Agent / LLM] B -->|Structured JSON Query| C[wellcontrol MCP Server] C -->|Deterministic Physics Engine| C C -->|Verified Exact Math| B B -->|Verified Output| D[Driller Console / Choke Panel] How the Layered Responsibility Works: The LLM's Role (Reasoning & Orchestration): Continuously monitors WITSML telemetry events (SPP spikes, pit gains, differential pressure changes). Identifies kick mechanisms, lost circulation anomalies, or drillstring pack-offs. Formulates the action plan in accordance with rig-specific SOPs.

The MCP Tool's Role (Deterministic Math & Physics): Computes exact hydrostatics, friction losses, multi-station torque and drag, and kill schedules. Operates with zero external network access and zero token randomness. Verified across hundreds of automated unit tests covering API RP 53, IADC, and IWCF benchmarks.

2. Real-World Implementation: The wellcontrol MCP Server Our wellcontrol repository implements an production-grade MCP server exposing 5 core operational tools:

# Example MCP Tool Definition in wellcontrol @mcp.tool () async def plan_well_kill ( method: str, depth_tvd_ft: float, current_mw_ppg: float, sidpp_psi: float, sicp_psi: float, scrp_psi: float, drillstring_vol_bbl: float, pump_output_bbl_stk: float ) -> dict [ str, Any ]: """ Calculates deterministic IADC WellSharp kill parameters. No LLM prediction: strictly verified deterministic formulas. """ # 1.

Kill Mud Weight with directional ceiling raw_kmw = current_mw_ppg + sidpp_psi / ( 0.052 * depth_tvd_ft ) kmw = math. ceil (( raw_kmw - 1e-9 ) * 10 ) / 10 # 2. ICP & FCP icp = round ( sidpp_psi + scrp_psi ) fcp = math. ceil (( scrp_psi * kmw / current_mw_ppg ) - 1e-9 ) # 3. Surface-to-bit displacement strokes strokes_to_bit = round ( drillstring_vol_bbl / pump_output_bbl_stk ) return { " method ": method, " kmw_ppg ": kmw, " icp_psi ": icp, " fcp_psi ": fcp, " strokes_to_bit ": strokes_to_bit, " pressure_drop_per_100_stk ": math. floor ((( icp - fcp ) * 100 / strokes_to_bit ) + 1e-9 ) } Enter fullscreen mode Exit fullscreen mode 3.

CI/CD Governance & RAG Evaluation Gates Even when tools provide exact mathematical answers, agents must synthesize them into coherent action checklists for the toolpusher or driller.

To prevent prompt drift or hallucinated section citations, we introduced sop-rag-judge:

Combining generative reasoning with deterministic tool execution is the foundational requirement for AI in high-hazard environments. By using MCP as the abstraction boundary between language models and physical formulas, we achieve the best of both worlds: autonomous operational insight with deterministic physical safety.

You can explore the live simulator at wellcontrol.kcklayton.com or inspect the MCP implementation on GitHub: 👉 github.com/Greybeard00007/wellcontrol