Skip to main content
Glama

AstroLogics

Manglik (Mangal) dosha check

check_manglik_dosha
Read-onlyIdempotent

Check Manglik (Mangal) dosha in a birth chart: whether Mars occupies a dosha house from the ascendant, Moon or Venus, its strength, and any classical cancellation. Requires birth date, birth time and coordinates (the ascendant depends on the time).

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": "check_manglik_dosha"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
timeYesLocal birth time, HH:MM. Required.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
latitudeYesBirth latitude in decimal degrees.
longitudeYesBirth longitude in decimal degrees.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.",
      +  "enum": [
      +    "en",
      +    "hi"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds the meaningful behavioral note that results depend on the birth time via the ascendant, but says nothing about output format, precision, or error conditions when time is approximate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what is checked, then the requirements and their rationale. No redundant or filler wording.

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?

With no output schema, the description does compensate by naming the returned findings (dosha presence, strength, cancellation), and the 100% schema coverage covers inputs. Minor gap: it does not indicate what the response structure looks like for multiple reference points (ascendant/Moon/Venus).

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an increment by justifying the time parameter (ascendant derivation) rather than merely restating that it is required. It does not explain the language parameter's effect, but the schema handles that enumeration.

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/Mangal dosha check) and enumerates exactly what is evaluated: Mars in a dosha house counted from the ascendant, Moon or Venus, plus strength and classical cancellation. This clearly separates it from sibling dosha checks like check_kaal_sarp_dosha and check_pitra_dosha.

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?

Gives concrete prerequisites (birth date, birth time, coordinates) and explains why time is mandatory, since the ascendant depends on it. It stops short of explicitly routing the agent away from alternatives such as check_marriage_compatibility, so there is no when-not guidance.

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