Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Yogas: Karakamsa chart (12-house projection)

astroway_vedic_yogas_jaimini_karakamsa
Read-onlyIdempotent

Calculate Jaimini Karakamsa houses from birth date, time, and coordinates to identify Ishta Devata and Moksha indicator yogas.

Instructions

Karakamsa = Atmakaraka's sign in D9 Navamsha, treated as lagna for a 12-house projection. Each house carries canonical iṣṭa-devata / moksha / spiritual significations per Sanjay Rath. Yogas surfaced: 5th-house planet = Ishta Devata; 12th-house planet = Moksha Indicator.

[Group: Vedic] [Endpoint: POST /v1/vedic/yogas/jaimini/karakamsa] [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_yogas_jaimini_karakamsa"
  }
}

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
lagnaNo
yogasNo
housesNo
karakamsaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

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, so safety is covered; the description adds the endpoint, the mandatory inputs, and the cost (20 credits, Tier 2) before invocation, which is genuinely useful pre-call context. It does not mention pagination or whether the response is a single chart or a per-house list, but the output schema covers returns.

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?

Front-loaded with the technique definition, then the yoga rules, then a compact bracketed metadata block for group/endpoint/required/cost. Two sentences plus metadata, no filler, though the Sanskrit terminology is dense for an uninitiated agent.

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 needn't be re-explained, and the cost/required-input metadata is a plus. However, for a 13-parameter, 23%-covered tool in a crowded Vedic/Jaimini namespace, the description leaves the agent without guidance on optional configuration or on sibling selection.

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 needs to compensate and does not. It only restates the four required fields, which the schema already marks as required, and says nothing about the eleven optional parameters (ayanamsa choice, houseSystem, zodiacType, timezone vs timezoneOffset, cosmogram) that materially change the computed chart.

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?

States a concrete technique (Karakamsa = Atmakaraka's D9 sign as lagna) and precisely what the output contains: a 12-house projection with iṣṭa-devata/moksha significations and the 5th/12th-house yoga rules. That distinguishes it from the general jaimini_yogas and atmakaraka_navamsa siblings by content, though neither is named as an alternative.

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 spiritual/moksha framing implies when the tool is relevant, and the '[Required: date, time, latitude, longitude]' line tells the agent what a call needs. But there is no explicit guidance on when to pick this over sibling tools such as astroway_vedic_jaimini_yogas or astroway_vedic_jaimini_atmakaraka_navamsa, which cover overlapping ground.

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