Advanced techniques

KP Compatibility Panel (CSL factors + dasha sync)

get_compatibility_panel

KP-rigorous compatibility for two partners (renamed from get_compatibility_advanced on 2026-10-08). Replaces Vedic Porutham (which KP rejects per Reader 4) with 6 factors: LOVE (5th CSL by 5th CSL into 2/5/11), MARRIAGE (7 by 7 into 2/7/11), FINANCE (2 by 2 into 2/11), UNION (11 by 11 into 2/7/11), DENIAL_ABSENCE (no 6/8/12 from 7th CSL), and DASHA_SYNC (overlapping 7th/11th-house dasha windows when both partners are simultaneously active in marriage-house periods). Returns '{ poruthamRejected, poruthamRejectionNote, theTenPoruthams, individualPrerequisites, prerequisiteNote, factors: [{ factor, score, verdict, person1Coverage, person2Coverage, rationale }], dashaSyncWindows: [{ fromDate, toDate, person1Mahadasha, person1Antardasha, person2Mahadasha, person2Antardasha, confidence, rationale }], overallScore, overallVerdict: EXCELLENT | GOOD | AVERAGE | BELOW_AVERAGE | POOR, summary, bookCitations, framesUsed, methodSeams }'. Every score is an engine construction (F006), and 'overallScore' is an unlabelled average across both claims; KSK's six individual-chart points ('individualPrerequisites') are a gate to read first, not weights. The two claims are also tools of their own: 'get_couple_csl_factors' (the first five factors) and 'get_couple_dasha_sync' (the windows and the DASHA_SYNC row).

Parameters

No parameters. This tool reads its inputs from the conversation context.

Example call

Send the request as a standard MCP tools/call:

POST https://mcp.lumin.guru/mcp
Authorization: Bearer mcp_yourkey...
Accept: application/json, text/event-stream
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_compatibility_panel",
    "arguments": {}
  }
}