Skip to main content
Glama

Doshas: Lal Kitab Manglik

astroway_vedic_doshas_lal_kitab_manglik
Read-onlyIdempotent

Manglik dosha per Lal Kitab, read from houses of the Lal Kitab chart (lagna = house 1), never from signs: Mars in house 1, 4, 7, 8 or 12. mars.inPakkaGhar is true in house 3 or 8, Mars's pakka ghar; it does not cancel the dosha. The one cancellation is Lal Kitab 1952 p. 76: Mars with Mercury in house 8 while Saturn is not in house 2.

[Group: Vedic] [Endpoint: POST /v1/vedic/doshas/lal-kitab/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_lal_kitab_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. 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
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
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
marsNo
doshaNo
remedyNo
schoolNo
presentNo
lagnaSignNo
disclaimerNo
cancellationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / mars / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "houseFromLagna": {
      -        "type": [
      -          "number",
      -          "null"
      -        ]
      -      },
      -      "sign": {
      -        "type": [
      -          "number",
      -          "null"
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "houseFromLagna": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "inPakkaGhar": {
      +        "type": [
      +          "boolean",
      +          "null"
      +        ]
      +      },
      +      "sign": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed15 schema fields changed
    • removedInput schema / properties / ayanamsaId / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / ayanamsaId / type
      Added value: +[
      +  "number",
      +  "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"
      +]
    • removedOutput schema / properties / lagnaSign / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / lagnaSign / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / mars / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "houseFromLagna": {
      -        "anyOf": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "sign": {
      -        "anyOf": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "houseFromLagna": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "sign": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / present / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / present / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • removedOutput schema / properties / remedy / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / remedy / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / school / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / school / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. First observed

TDQS

A3.8/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, so the bar is lower, and the description goes well beyond them by disclosing the exact detection rule, the pakka-ghar nuance that does NOT cancel the dosha, and the single sourced cancellation exception. That is real domain context an agent could not recover from structured fields. It stops short of describing response shape, but an output schema exists so that gap is minor.

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 rule, then the exception case, with no filler; the bracketed group/endpoint/required/cost block is scannable. Slightly dense astrological shorthand, but each sentence carries information an interpreting agent needs.

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

Completeness4/5

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

For a single-dosha calculator with an output schema, the definition fully specifies how the verdict is derived and cancelled, which is the hard part. What is missing is caller-facing input guidance across the 15-parameter surface, though the required set is enumerated in the context line.

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?

Fifteen parameters at 33% schema description coverage, and the description says nothing about any of them — not the required date/time/latitude/longitude, not timezone vs timezoneOffset precedence, not ayanamsa selection, not the compact-mode fields/precision pair. The only parameter-adjacent content is the mention of `mars.inPakkaGhar`, a response field path, which does not compensate for the coverage gap.

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

Purpose5/5

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

States a specific verb and resource ('Manglik dosha per Lal Kitab, read from houses of the Lal Kitab chart') and pins the method that separates it from the other manglik tools in the catalog: house-based, never sign-based. An agent can tell this apart from the KP and Parashara manglik siblings without opening any schema.

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 Lal Kitab school and the 'lagna = house 1' frame imply when this is the right tool, but there is no explicit when-to-use, no exclusion, and no named alternative (e.g. lal_kitab_full or the KP/Parashara manglik variants). Usage is inferable rather than stated.

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