AstroWay Vedic astrology

Jaimini: Karakamsa (AK in Navamsa)

astroway_vedic_jaimini_atmakaraka_navamsa

Read-onlyIdempotent

Karakamsa: sign occupied by the Atmakaraka in the Navamsa (D9). Per Jaimini Sutras 1.2: indicates soul-level destiny, deity worship orientation, primary spiritual path.

[Group: Vedic] [Endpoint: POST /v1/vedic/jaimini/atmakaraka-navamsa] [Required: date, time, latitude, longitude] [Cost: 20 credits (Tier 2)]

Input Schema

Name	Required	Description	Default
`city`	No
`date`	Yes
`name`	No
`time`	Yes
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`latitude`	Yes
`timezone`	No	IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
`cosmogram`	No
`longitude`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`ayanamsaId`	No
`zodiacType`	No
`houseSystem`	No		P
`timezoneOffset`	No	Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

Name	Required	Description	Default
`ak`	No
`lagna`	No
`akName`	No
`d9Sign`	No
`meaning`	No
`d9SignName`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedNov 7, 2026

removedInput schema / properties / ayanamsaId / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / ayanamsaId / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / ak / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / ak / type

Added value: +[
+  "number",
+  "null"
+]

removedOutput schema / properties / akName / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / akName / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / d9Sign / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / d9Sign / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / d9SignName / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / d9SignName / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / lagna / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "sign": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "signName": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "sign": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "signName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / meaning / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / meaning / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedOct 5, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds genuinely new operational context: the endpoint, the four required inputs, and a cost of 20 credits (Tier 2), which matters for an agent deciding whether to spend a call. It does not mention defaults that affect output (e.g. Lahiri ayanamsa) or any caching, so it stops short of full disclosure.

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 core definition is front-loaded in a single dense sentence, with the bracket metadata block kept short and scannable. The metadata (group, endpoint, cost) earns its space, though the required-parameters line is redundant with the schema.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the tool's computational purpose is fully stated. However, for a 15-parameter tool where sidereal school, zodiac type, and timezone handling materially change the result, the description gives no guidance on those choices beyond noting which fields are mandatory.

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 only about 33% across 15 parameters, so the description must compensate and does not. Its '[Required: date, time, latitude, longitude]' line merely restates the schema's required array, and it says nothing about the astrologically consequential options (ayanamsa/ayanamsaId, zodiacType, houseSystem, fields, precision, timezone vs timezoneOffset).

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

Purpose4/5

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

The description names the specific artifact (Karakamsa = the sign held by the Atmakaraka in the Navamsa/D9) and states what it signifies, citing Jaimini Sutras 1.2. It is clear what is being computed, though it does not distinguish itself from nearby siblings such as astroway_vedic_varga_d9 or astroway_vedic_yogas_jaimini_karakamsa.

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

Usage Guidelines3/5

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

Usage is only implied through the interpretive framing (soul-level destiny, deity worship orientation, spiritual path), which suggests spiritual/dharmic questions are the target use case. There is no explicit when-to-use statement, no exclusions, and no pointer to an alternative tool when a plain D9 chart or a karakamsa-yoga analysis is what the user actually wants.

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

All AstroWay Vedic astrology tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?