Gated two-step chain for NAIC RBC action level determination and claims STP economic triage. Step 1 computes the RBC action level (NO_ACTION / COMPANY_ACTION / REGULATORY_ACTION / AUTHORIZED_CONTROL / MANDATORY_CONTROL) from Total Adjusted Capital and Authorized Control Level inputs. The §21.4 decision gate reads /action_level_code: NO_ACTION exits the chain immediately (no remediation analysis needed); any triggered level proceeds to step 2, which models claims STP economics to quantify cost-reduction potential from automation under financial stress. Both branches recorded in decisions[].
compute_rbc_action_level{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "compute_rbc_action_level",
"arguments": {
"total_adjusted_capital": 180000000,
"authorized_control_level_rbc": 100000000,
"prior_year_tac": 220000000,
"insurer_type": "life"
}
},
"id": 1
}
calculate_claims_stp_economics{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "calculate_claims_stp_economics",
"arguments": {
"annual_claims_volume": 50000,
"manual_cost_per_claim": 85,
"stp_cost_per_claim": 12,
"current_stp_rate": 0.35,
"target_stp_rate": 0.80,
"implementation_cost": 2500000,
"discount_rate": 0.10,
"projection_years": 5
}
},
"id": 2
}
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.
Question: The year-end ratio is filed. Which NAIC RBC action level does the company land on, and how far is the next trigger?
Run the AINumbers MCP tool `run_chain` with {"chain":"insurer-rbc-action-level"} and read `art-254-compute-rbc-action-level.action_level_code`.
Re-run with `inputs` for `art-254-compute-rbc-action-level`, reusing the values that result echoed, with `total_adjusted_capital` set to 60000000. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/insurer-rbc-action-level.html