Nakshatra Details

asterwise_get_nakshatra_details

Looks up static metadata for one of twenty-seven nakshatras by name and returns interpretive, professional, activity, and body-map reference data.

Parameters

Parameter	Type	Required	Description
nakshatra_name	string	yes	Nakshatra name, e.g. 'Rohini' or 'Uttara Phalguni'.
response_format	enum: markdown, json	no	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.

What it covers

Vedanga/classical reference only — no chart computation. Covers deity, ruler, symbol, gana, nature, classical vs modern prose, profession vectors, life themes, keywords, strengths/challenges, favourable vs unfavourable activities, and body_map. Names are case-sensitive exact matches (Ashwini … Revati list). It does not compute birth nakshatra from BirthData (use asterwise_get_natal_chart).

Workflow

BEFORE: None — this tool is standalone.
AFTER: None.

Input

nakshatra_name is sent as given; the API ignores case, spaces, hyphens and common romanisation differences ('uttarashadha', 'Aswini', 'Moola' and 'Krithika' all match). An unknown name returns 404 with the 27 valid names and, for a near miss, a suggestion.

Output contract

data.name (string)
data.index (int — 0–26)
data.interpretation:
source (string)
nakshatra_number (int)
name (string)
sanskrit (string)
span (string)
symbol (string)
deity (string)
ruling_planet (string)
sign (string)
sign_lord (string)
gana (string)
nature (string)
body_part (string)
classical_qualities[] (string array)
appearance — { classical (string), modern (string) }
nature_description — { classical (string), modern (string) }
profession — { primary[] (string array), secondary[] (string array), note (string), modern (string) }
life_themes — { core, karmic_path, challenge, gift, modern (strings) }
keywords[] (string array)
strengths[] (string array)
challenges[] (string array)
padas[] — { pada (int), span (string), navamsa_sign (string), navamsa_lord (string), vargottama (bool), special_note (string — names Gandanta, Vargottama and Pushkara Navamsa; 24 Pushkara padas per the standard rule) }
data.activities:
favorable_activities[] (string array)
unfavorable_activities[] (string array)
data.body_map:
parts[] (string array)
sensitivity (string)

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

FAST_LOOKUP

Errors

INVALID_PARAMS (local — caught before upstream call):
None — name passes straight through.

INVALID_PARAMS (upstream):
— None — unknown names surface as MCP INTERNAL_ERROR at the tool layer.

INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR

Edge cases:
— Names outside the 27 (e.g. regional names such as 'Thiruvonam') are not matched; use the listed Sanskrit names.

Do not confuse with

asterwise_get_natal_chart — computes birth nakshatra from time/place, not encyclopaedic copy.
asterwise_get_dasha — uses Moon nakshatra for timing, not this lookup table.

Connect

Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.