Advanced techniques

Complete Kundli Matching Workflow

run_kundli_match_complete

Atomic comprehensive matrimonial matching for matrimonial-platform B2B. Reports THREE compatibility columns side by side, which answer different questions: 36-pt Vedic Ashta Koota (Varna+Vashya+Tara+Yoni+Graha-Maitri+Gana+Bhakoota+Nadi, Parashari, which KP Reader 4 rejects), KP-rigorous 6-CSL-factor (LOVE/MARRIAGE/FINANCE/UNION/DENIAL/DASHA-SYNC, with KSK's six individual-chart prerequisites), and the Jaimini Upapada Lagna relationship, plus the Parashari Manglik check on both partners. Returns '{ ashtaKoota, kpRigorousCompatibility, manglikCheck, upapadaLagnaRelationship, synthesis: { systems[], disagreementType, overallVerdict, confidenceBand, crossSystemConcordance: STRONG|PARTIAL|DIVERGENT, scoreProvenance } }'. Read 'synthesis.systems' per column; the concordance, verdict and band are a count of three flags, a labelled Lumin convention, not a consensus any of the three systems makes. The matrimonial flagship workflow. In the Ashta Koota the user's own chart is scored as the groom and the partner as the bride (see get_ashta_koota_milan's groomConvention).

Parameters

Name	Type	Required	Description
birth_datetime	string	Yes	Birth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitude	number	Yes	Birth location latitude. Range: -90 to 90.
longitude	number	Yes	Birth location longitude. Range: -180 to 180.
utc_offset_minutes	number	Yes	UTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsa	enum: kp \| kp_new \| lahiri \| raman \| true_chitra \| khullar	No	Ayanamsa system. Defaults to kp.
partner	object	Yes	Partner birth data.

Example call

Send the request as a standard MCP tools/call:

http

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": "run_kundli_match_complete",
    "arguments": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp"
    }
  }
}

Birth data

This tool requires birth data on every call. The MCP server is stateless, so calling set_birth_profile first validates the data and returns the reading plan, but it does not store anything. Repeat the same five fields here.