Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Jaimini: Karakamsa (AK in Navamsa)

astroway_vedic_jaimini_atmakaraka_navamsa
Read-onlyIdempotent

Determine the Karakamsa sign by locating the Atmakaraka in the Navamsa (D9) to reveal soul-level destiny, deity worship orientation, and primary spiritual path.

Instructions

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)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "time": "<time>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_vedic_jaimini_atmakaraka_navamsa"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA 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.
cosmogramNo
longitudeYes
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
timezoneOffsetNoHours 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

NameRequiredDescriptionDefault
akNo
lagnaNo
akNameNo
d9SignNo
meaningNo
d9SignNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful non-schema context, namely the credit cost (20, Tier 2) and the endpoint, but it does not disclose defaults that materially affect output (Lahiri ayanamsa, sidereal zodiac, P house system) or timezone resolution behavior.

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 the first sentence, followed by terse bracketed metadata. No filler sentences, though the endpoint/cost scaffolding is a tag block rather than prose and slightly clutters the reading flow.

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?

For a single-point Jaimini calculation with an output schema present, the description covers meaning, required inputs, and cost. It leaves notable gaps: how ayanamsa/zodiac/house-system choices change the result, and how this differs from the karakamsa-yoga sibling, are unaddressed.

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 23% across 13 parameters, so the description is expected to compensate and it does not. It merely restates the four required parameters and says nothing about the nine optional ones (ayanamsa vs ayanamsaId, timezone vs timezoneOffset precedence, houseSystem enum codes, cosmogram, zodiacType).

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 its interpretive meaning, which lets an agent distinguish it from the broader Jaimini yoga sibling astroway_vedic_yogas_jaimini_karakamsa. It stops short of explicitly contrasting with that sibling, so it is clear but not fully differentiated.

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?

The phrase about soul-level destiny and primary spiritual path implies the use case (spiritual/destiny questions) but never states when to choose this over the many other Jaimini/Navamsa tools, nor any prerequisites or exclusions. Usage must be inferred from the interpretive sentence.

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

Deploy Server

Other Tools