Skip to main content
Glama

AstroWay Astrology API (full catalogue)

Doshas: KP Manglik

astroway_vedic_doshas_kp_manglik
Read-onlyIdempotent

Manglik dosha with KP sub-lord precision attached. Sub-lord chain of Mars added for transit-trigger analysis.

[Group: Vedic] [Endpoint: POST /v1/vedic/doshas/kp/manglik] [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_doshas_kp_manglik"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
ayanamsaNoSidereal school by name. Krishnamurti ("kp") when omitted on KP routes. 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
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
ayanamsaIdNoSidereal mode, the standard numeric ayanamsa ids. 5 (Krishnamurti) when omitted on KP routes; 1 is Lahiri.
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
doshaNo
schoolNo
detailsNo
presentNo
severityNo
kpSubLordNo
lagnaSignNo
disclaimerNo
affectedHousesNo
contributingPlanetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ayanamsaId / description
      Previous value: -"Swiss Ephemeris sidereal mode. 5 (Krishnamurti) when omitted on KP routes; 1 is Lahiri."New value: +"Sidereal mode, the standard numeric ayanamsa ids. 5 (Krishnamurti) when omitted on KP routes; 1 is Lahiri."
  2. Changed2 schema fields changed
    • changedInput schema / properties / ayanamsa / description
      Previous value: -"Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either."New value: +"Sidereal school by name. Krishnamurti (\"kp\") when omitted on KP routes. Equivalent to ayanamsaId; send either."
    • addedInput schema / properties / ayanamsaId / description
      Added value: +"Swiss Ephemeris sidereal mode. 5 (Krishnamurti) when omitted on KP routes; 1 is Lahiri."
  3. Changed18 schema fields changed
    • removedInput schema / properties / ayanamsaId / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / ayanamsaId / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / affectedHouses / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "number"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / contributingPlanets / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": {},
      -          "properties": {
      -            "graha": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "house": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "planetName": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "sign": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "graha": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "house": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "planetName": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "sign": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / details / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / disclaimer / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / disclaimer / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / dosha / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / dosha / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / kpSubLord / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "sign": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "star": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "sub": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "subSub": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "sign": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "star": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "sub": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "subSub": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / lagnaSign / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / lagnaSign / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / present / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / present / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • removedOutput schema / properties / school / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / school / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / severity / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / severity / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  4. First observed

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 and closed-world, so the safety profile is covered. The description adds genuinely useful operational context — 20 credits (Tier 2) and the POST endpoint — but says nothing about whether the result is a boolean flag, a severity scale, or the raw sub-lord chain, which matters for a scored dosha tool.

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 two sentences are front-loaded and dense with the differentiating information, and the bracketed metadata block is scannable. The [Required: ...] line is somewhat redundant against the schema, but overall there is little waste.

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 15-parameter computation tool with an output schema present, the description covers the conceptual intent but omits how to choose among the three manglik dosha variants and what the KP-specific payload adds in practice. It is adequate to identify the tool, marginally adequate to call it well.

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 40% across 15 parameters, so the description should compensate, yet it only restates the four required fields already marked required in the schema. Nothing is said about how ayanamsa/ayanamsaId defaults to Krishnamurti on KP routes, or how fields/precision shaping affects the response, leaving the most consequential knobs undocumented.

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 resource (Manglik dosha) and pins down its differentiator: KP sub-lord precision with the sub-lord chain of Mars, which separates it from the Lal Kitab and Parashara manglik siblings. It stops short of explicitly naming those alternatives, but an agent can infer the KP variant from the text.

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?

'Added for transit-trigger analysis' implies a use case, so there is a hint of when this variant is worth the higher cost. However, there is no explicit when-to-use rule, no exclusion of the lal_kitab/parashara manglik tools, and no note on prerequisites such as birth data accuracy — usage is only implied.

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