Advanced techniques
Service against Business, Five Sourced Rules Side by Side (KP)
get_job_vs_business_verdict
Answers salaried service against running one's own concern by running five sourced KP rules independently and reporting each one, in the style of get_four_step_verdict. Rule A: the 2nd cusp sub lord clauses (KP Reader 3 p.154, restated Reader 5 p.175). Rule B: the star lord of the 10th CSL against the 6th and the 7th (Jyotish Part 1 p.345, Part 3 p.058). Rule C: the 10th CSL on 6-8 against 7-10-11 (Part 1 p.355). Rule D: the 6-8-12 group against the 1-7-10-11 group, compared as fractions (Part 1 p.382). Rule E: the applied exclusion sets through the 10th CSL's star lord, with the 6th-CSL and 11th-CSL fallback chain. Returns '{ verdicts[], consensus, agreement: STRONG|PARTIAL|DIVERGENT, denialGate, dualProfession, strictStellarFilterApplied, summary, disclaimer }'. Also enforces the Part 1 p.359 denial gate (a 10th CSL signifying none of 6, 7 or 10 promises no settled occupation) and the Part 1 p.356 strict stellar filter (a star lord must signify by occupation, or be in its own star as owner; mere ownership does not count), reporting which significations the filter dropped. When the rules disagree the disagreement is the answer: this tool never picks a winner silently.
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. |
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_job_vs_business_verdict",
"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.