Skip to main content
Glama

Supastro

Find the Jaimini karakas and padas

get_jaimini_karakas
Read-onlyIdempotent

Calculates the Jaimini factors of a birth chart: the seven chara karakas from Atmakaraka to Darakaraka with each planet's degree, the Karakamsa (the Atmakaraka's Navamsa sign), the Arudha Lagna, and the Upapada Lagna with the planets in or aspecting it and the sign after it. It also flags when a small birth-time error would change which planet is the Atmakaraka. Use it when someone asks for their Atmakaraka, Darakaraka or other chara karaka, their Karakamsa, their Arudha Lagna or their Upapada Lagna.

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": {
      "birth_date": "<birth_date>",
      "birth_time": "<birth_time>",
      "birth_place": "<birth_place>"
    },
    "name": "get_jaimini_karakas"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeNoOptional. Latitude of the birth place in decimal degrees, north positive. Give it only together with longitude, when the user supplied coordinates or the place could not be found by name.
longitudeNoOptional. Longitude of the birth place in decimal degrees, east positive. Give it only together with latitude.
birth_dateYesDate of birth as YYYY-MM-DD, for example 1990-01-15 for 15 January 1990. People write dates in different orders: day first in India and most countries, month first in the United States. Convert what the person wrote to YYYY-MM-DD yourself. If an all-number date could be read two ways, such as 05-06-1990, ask which number is the day before calling; never assume.
birth_timeYesLocal clock time of birth at the birth place, 24-hour HH:MM, for example 10:30, or 16:26 for 4:26 PM. If the person gave an hour from 1 to 12 without AM or PM, ask which before calling. Ask the user if the time is unknown; do not guess it.
birth_placeYesCity and country of birth, for example "Mumbai, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 computation, so the safety profile is covered. The description still adds real behavioral value: it discloses the birth-time-sensitivity flag ('flags when a small birth-time error would change which planet is the Atmakaraka') and describes the Upapada content (planets in or aspecting it, plus the following sign). That edge-case disclosure is exactly the kind of context annotations cannot carry.

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?

Two sentences, front-loaded with the computation and followed by usage triggers; no filler or marketing language. The output enumeration is long but each item is a distinct, non-redundant deliverable, so the density is earned rather than padded.

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?

With no output schema and five parameters, the description correctly carries the return-value burden by naming every component produced. Combined with the schema's input handling and the annotations' safety profile, an agent has everything needed to select and call this tool correctly.

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

Parameters3/5

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

Schema description coverage is 100% and the schema already carries the disambiguation coaching (ambiguous date order, 12-hour times, latitude/longitude pairing). The description mentions none of the five parameters and adds no meaning beyond the schema. Baseline 3 applies when the schema does all the work.

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?

Uses a specific verb and resource ('Calculates the Jaimini factors of a birth chart') and then enumerates the exact outputs: seven chara karakas with degrees, Karakamsa, Arudha Lagna, and Upapada Lagna. An agent knows precisely what comes back. It loses a point because the sibling get_arudha_padas overlaps on Arudha/Upapada territory and the description makes no attempt to separate the two.

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

Usage Guidelines4/5

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

The closing sentence gives concrete user-phrasing triggers: asks for Atmakaraka, Darakaraka, other chara karaka, Karakamsa, Arudha Lagna, or Upapada Lagna. That is a clear when-to-use rule. It stops short of any when-not or alternative routing, notably toward get_arudha_padas or get_navamsa_chart, which an agent would reasonably want here.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources