Advanced techniques

Mantra Recommendation (Parashari graha-shanti, planet-specific + bhadhaka)

get_mantra_recommendation

[Vedic Parashari] Graha-shanti mantras, the BPHS remedial practice, not KP: the KP Readers carry no mantra rule, and KSK refuses remedies (evils "cannot be averted, dodged or prevented by doing Shanthi", Reader 3 canon p.271; Reader 6 canon p.328). Scores every planet for affliction by retrogression and 6/8/12 placement; combustion and dignity are FLAGGED and not scored, because propitiating a planet for its debilitation is later Vedic remedial accretion with no footing in orthodox KP, which selects by cuspal sub lord and ruling planets (F066, Q023 section 21). Emits remedial mantras for the most-afflicted planet, the bhadhakasthana lord (always), and any secondary affliction. Each recommendation includes beejMantra, extendedMantra (Vedic stotram), recommended weekday, repetition count (108), 40-day duration, and rationale. Parashari mitigation practice, not a cure or a guarantee; never present it as a KP remedy.

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:

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": "get_mantra_recommendation",
    "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.