Gemstone Recommendations
asterwise_get_gemstone_recommendations
Computes Ratna-style gemstone picks and cautions from the natal chart and returns primary, role-based stones, secondary options, contraindications, and a safety note.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
birth | object | yes | Birth data for a single person. Fields: date, time, lat, lon*, person_name, timezone, ayanamsa |
response_format | enum: markdown, json | no |
What it covers
Surfaces data.primary, yogakaraka/fifth/ninth/atmakaraka gems, secondary, contraindicated[], and note. Gemstone may be an empty string in primary when dual lordship withholds a recommendation. It does not emit mantra or fasting guidance (asterwise_get_remedies) or Lal Kitab totkas (asterwise_get_lal_kitab_remedies). The same mineral may appear in secondary and contraindicated with different reasons — read reason fields.
Workflow
BEFORE: RECOMMENDED — asterwise_get_natal_chart — confirm chart before wearing advice.
AFTER: asterwise_get_remedies — broader remedial programme if needed.
Input
BirthData follows the global contract.
Output contract
data.primary:
planet (string)
reason (string)
gemstone (string — may be empty when withheld for dual lordship)
substitute_gemstone (string)
metal (string)
colour (string)
note (string)
caution (string)
data.yogakaraka_gem — { planet (string), gemstone (string) }
data.fifth_lord_gem — { planet (string), gemstone (string) }
data.ninth_lord_gem — { planet (string), gemstone (string) }
data.atmakaraka_gem — { planet (string), gemstone (string) }
data.secondary — { planet (string), gemstone (string) }
data.contraindicated[] — { planet (string), gemstone (string), reason (string) }
data.note (string — safety disclaimer)
Response format
response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode.
Compute class
MEDIUM_COMPUTE
Errors
INVALID_PARAMS (local — caught before upstream call):
None — all validation is upstream.
INVALID_PARAMS (upstream):
— Dates before 1800 or after 2100 → MCP INTERNAL_ERROR at the tool layer.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— Gemstone duplication across secondary and contraindicated is intentional when roles conflict.
Do not confuse with
asterwise_get_remedies — mantras, fasting, charity rows, not a gem matrix.
asterwise_get_lal_kitab_remedies — Lal Kitab actions, not classical Ratna picks.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.