Asterwise

Natal Crystal Recommendations

asterwise_get_crystal_recommendations_natal

Read-onlyIdempotent

Recommends crystals from a Vedic natal chart using house lordship rules for gem selection. This is the only API that derives crystal recommendations from a computed natal chart — not from zodiac sign or chakra preference.

WORKFLOW: BEFORE: None — this tool internally computes the natal chart. No separate natal chart call required. AFTER: asterwise_get_crystal — get full detail (hardness, origins, affirmation, full caution text) on any recommended crystal by slug. AFTER: asterwise_get_remedies — broader classical remedial programme alongside gem recommendations.

INPUT CONTRACT: Standard BirthData (date, time, lat, lon, timezone, ayanamsa). Defaults to Lahiri ayanamsa. time (required): Ascendant (Lagna) is time-sensitive. Inaccurate birth time changes the Lagna → changes all house lords → changes recommendations entirely.

DO NOT CONFUSE WITH: asterwise_get_gemstone_recommendations — also a chart-based gem endpoint with the same contraindication rule, but a role-based prescription (lagna lord, Yogakaraka, 5th/9th lord, Atmakaraka) instead of crystal scoring; returns gem names not crystal database entries; does not include match_score or match_reasons. asterwise_get_crystal_recommendations — recommends crystals by zodiac sign, chakra, or intention keyword (no natal chart computation; Western metaphysical matching, not classical Jyotish). asterwise_get_crystal_by_planet — lists all crystals for a Vedic planet without house context — use this for reference, not prescription.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-crystal-recommendations-natal/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`birth`	Yes	Birth data for tools that need the exact birth time (no sunrise fallback).
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / birth / description

Previous value: -"Birth data for tools that need the exact birth time.\n\nTheir API endpoints have no sunrise fallback and reject a request without\na time, so the time is required here instead of failing upstream."New value: +"Birth data for tools that need the exact birth time (no sunrise fallback)."

Changed7 schema fields changedOct 6, 2026

changedInput schema / properties / birth / description

Previous value: -"Birth data for a single person."New value: +"Birth data for tools that need the exact birth time.\n\nTheir API endpoints have no sunrise fallback and reject a request without\na time, so the time is required here instead of failing upstream."

removedInput schema / properties / birth / properties / time / anyOf

Removed value: -[
-  {
-    "pattern": "^\\d{2}:\\d{2}$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / birth / properties / time / default
```
Removed value: -null
```

changedInput schema / properties / birth / properties / time / description

Previous value: -"Birth time HH:MM (24h), e.g. '06:45'. Omit if unknown (a sunrise chart is used and birth_time_provided=false); never pass '00:00' for unknown."New value: +"Birth time HH:MM (24h), e.g. '06:45'. Required: this tool has no sunrise fallback. If the user doesn't know it, say so rather than guessing; never pass '00:00' for unknown."

addedInput schema / properties / birth / properties / time / pattern
```
Added value: +"^\\d{2}:\\d{2}$"
```
addedInput schema / properties / birth / properties / time / type
```
Added value: +"string"
```

changedInput schema / properties / birth / required

Previous value: -[
-  "date",
-  "lat",
-  "lon"
-]New value: +[
+  "date",
+  "time",
+  "lat",
+  "lon"
+]

Changed1 schema field changedSep 5, 2026

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

Changed8 schema fields changedSep 4, 2026

changedInput schema / properties / birth / properties / date / description

Previous value: -"Birth date in YYYY-MM-DD format. Example: '1985-11-12'"New value: +"Birth date YYYY-MM-DD."

changedInput schema / properties / birth / properties / lat / description

Previous value: -"Birth latitude in decimal degrees. North positive, south negative. Example: 19.0760 for Mumbai, -33.8688 for Sydney"New value: +"Latitude in decimal degrees, north positive (Mumbai 19.076)."

changedInput schema / properties / birth / properties / lon / description

Previous value: -"Birth longitude in decimal degrees. East positive, west negative. Example: 72.8777 for Mumbai, -74.0060 for New York"New value: +"Longitude in decimal degrees, east positive (Mumbai 72.8777)."

changedInput schema / properties / birth / properties / person_name / description

Previous value: -"Name of the person for this chart. Example: 'Arjun Mehta'"New value: +"Person's name, used in labels only."

changedInput schema / properties / birth / properties / time / description

Previous value: -"Birth time in HH:MM 24-hour format. Example: '06:45'. Omit entirely if the birth time is unknown: a sunrise chart is used and birth_time_provided returns false. Do not pass '00:00' for an unknown time, it is treated as a real midnight birth and returns a confidently wrong ascendant."New value: +"Birth time HH:MM (24h), e.g. '06:45'. Omit if unknown (a sunrise chart is used and birth_time_provided=false); never pass '00:00' for unknown."

changedInput schema / properties / birth / properties / timezone / description

Previous value: -"IANA timezone for the birth location. Examples: 'Asia/Kolkata' (India), 'America/New_York' (New York), 'Europe/London' (London), 'Asia/Tokyo' (Japan), 'America/Los_Angeles' (Los Angeles), 'Europe/Paris' (Paris), 'Asia/Dubai' (Dubai), 'Asia/Singapore' (Singapore), 'America/Chicago' (Chicago), 'Australia/Sydney' (Sydney). Default: Asia/Kolkata"New value: +"IANA timezone of the birth place, e.g. 'Asia/Kolkata', 'America/New_York', 'Europe/London'. Default: Asia/Kolkata"

addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```

changedInput schema / required

Previous value: -[
-  "birth",
-  "response_format"
-]New value: +[
+  "birth"
+]

Changed6 schema fields changedJul 25, 2026

addedInput schema / properties / birth / properties / time / anyOf

Added value: +[
+  {
+    "pattern": "^\\d{2}:\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / birth / properties / time / default
```
Added value: +null
```

changedInput schema / properties / birth / properties / time / description

Previous value: -"Birth time in HH:MM format (24-hour). Example: '06:45'. Use '00:00' if unknown."New value: +"Birth time in HH:MM 24-hour format. Example: '06:45'. Omit entirely if the birth time is unknown: a sunrise chart is used and birth_time_provided returns false. Do not pass '00:00' for an unknown time, it is treated as a real midnight birth and returns a confidently wrong ascendant."

removedInput schema / properties / birth / properties / time / pattern
```
Removed value: -"^\\d{2}:\\d{2}$"
```
removedInput schema / properties / birth / properties / time / type
```
Removed value: -"string"
```

changedInput schema / properties / birth / required

Previous value: -[
-  "date",
-  "time",
-  "lat",
-  "lon"
-]New value: +[
+  "date",
+  "lat",
+  "lon"
+]

AddedMay 3, 2026

TDQS

Score is being calculated.

All Asterwise tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?