Asterwise

Natal Chart

asterwise_get_natal_chart

Read-onlyIdempotent

Computes the full sidereal natal chart from BirthData and returns planet rows, houses, aspects, arudhas, upapada, bhava cusps, and avakhada metadata.

WORKFLOW: BEFORE: None — this tool is standalone. AFTER: RECOMMENDED — asterwise_get_yogas — layer classical combinations after the base chart exists.

INPUT CONTRACT: BirthData enforces date YYYY-MM-DD, time HH:MM, lat -90..90, lon -180..180, ayanamsa enum locally (Pydantic). Unknown birth time may be entered as time='00:00' without error; lagna-sensitive results are then unreliable and callers must handle that — the API does not flag it.

DO NOT CONFUSE WITH: asterwise_get_divisional_chart — sixteen vargas only, not the primary radix bundle returned here.

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`birth`	Yes	Birth data for a single person.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown
`include_interpretation`	No	Include a written interpretation alongside the chart data.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedSep 5, 2026

addedInput schema / properties / include_interpretation / description

Added value: +"Include a written interpretation alongside the chart data."

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"
+]

First observedApr 22, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description goes beyond this by disclosing that unknown birth time can be passed as '00:00' without error but that lagna-sensitive results become unreliable, and that the API does not flag this. It also links to the full output and error contract, adding meaningful behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE, docs link) and front-loads the core purpose. It is somewhat dense and repeats validation details already present in the schema, but for a complex tool with nested parameters, the organization earns its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, the description covers what the tool returns, workflow sequencing, the closest sibling alternative, a critical input caveat, and a link to the full output/error contract. An agent has enough context to invoke it correctly, apart from the time='00:00' contradiction noted above.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. However, the description's INPUT CONTRACT states 'Unknown birth time may be entered as time='00:00' without error', which directly contradicts the schema's explicit instruction to 'Omit if unknown' and 'never pass "00:00" for unknown'. This is actively misleading and likely to cause incorrect tool invocation despite the high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Computes the full sidereal natal chart from BirthData' and enumerates the exact output components (planet rows, houses, aspects, arudhas, upapada, bhava cusps, avakhada metadata). It also explicitly distinguishes itself from asterwise_get_divisional_chart, so an agent can clearly separate this tool from its closest sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The WORKFLOW section states this tool is standalone before, and recommends asterwise_get_yogas after, giving sequencing guidance. The 'DO NOT CONFUSE WITH' section explicitly names asterwise_get_divisional_chart and explains the difference, satisfying the when-to-use vs alternative requirement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Asterwise tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

Many tools are well-differentiated by explicit 'DO NOT CONFUSE WITH' notes, but the sheer number of near-neighbor pairs (e.g., crystal vs gemstone recommendations, natal chart variants, dasha systems, compatibility systems, tarot draw variants) creates real selection risk. The descriptions mitigate overlap, but an agent browsing 103 tools will struggle to pick the right one.

Naming Consistency5/5

Every tool follows the asterwise_get_* or asterwise_draw_* prefix convention with a clear noun phrase (e.g., asterwise_get_natal_chart, asterwise_draw_tarot_cards). The two verbs 'get' and 'draw' are semantically appropriate, and there are no camelCase or mixed-style names.

Tool Count1/5

103 tools is far beyond a manageable MCP surface. While the domain is broad (Vedic astrology, Western astrology, numerology, tarot, crystals, dream symbols), the server bundles multiple distinct domains into one namespace, making it nearly impossible for an agent to discover the right tool efficiently.

Completeness4/5

The surface is impressively comprehensive across astrology, numerology, tarot, and remedies, with deep coverage of dasha systems, compatibility frameworks, and chart types. Minor gaps exist (e.g., no tarot interpretation endpoint, no batch operations, no update/delete since it's read-only data), but for a reference/prediction API the coverage is strong.

Resources

Need Help?