VedicDost: Vedic Astrology, Kundli & AI Astrologer

Dosha check (Manglik, Sade Sati, Kaal Sarp)

check_dosha

Read-onlyIdempotent

Checks a birth chart with VedicDost's software for Manglik (Kuja) dosha from Lagna and Moon, Saturn's Sade Sati or Dhaiya running now, Kaal Sarp, Pitra and Gandmool. Gives honest, non-fear wording and the classical basis. Use for "am I manglik", "is sade sati running", "do I have kaal sarp dosh".

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>"
    },
    "name": "check_dosha"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Birth date, YYYY-MM-DD
`time`	No	Birth time HH:MM, 24-hour local clock time (optional; without it Lagna and houses are skipped)
`place`	No	Birth place: an Indian city ("Satna") or "City, Country" anywhere ("London, United Kingdom")
`language`	No	User language: hi, en, mr, gu, bn, ta, te or kn (default en). Text comes in Hindi for hi and English otherwise; links open the VedicDost page in this language. Reply to the user in their own language.
`latitude`	No	Optional, instead of place
`timezone`	No	Optional IANA zone (e.g. Asia/Kolkata); found from the place if left out
`longitude`	No	Optional, instead of place

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

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 and closed-world, so safety is covered. The description adds genuinely non-structured context: results are framed in 'honest, non-fear wording' and include 'the classical basis', which tells the agent what kind of output to expect and how to present it. It stops short of describing the response structure or how multiple doshas are returned.

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 with no filler: the first declares the computation and its astrological basis, the second supplies example user queries. Everything is front-loaded and each clause earns its place.

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 seven parameters, one required, and no output schema, the description covers what is computed and the tone of the result, which is enough to call it correctly. It does not sketch the return shape (per-dosha verdicts, remedies, links) despite there being no output schema to supply that.

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%, with date, time, place, coordinates, timezone and language all documented, including the consequence of omitting time. The description adds only the implicit note that Lagna- and Moon-based calculation depends on birth data, so the schema carries nearly all the semantic weight and the baseline 3 applies.

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 a specific verb ('Checks a birth chart') and enumerates the exact doshas computed (Manglik/Kuja from Lagna and Moon, Sade Sati/Dhaiya running now, Kaal Sarp, Pitra, Gandmool), so the scope is unambiguous. It does not explicitly contrast itself with get_kundli or dasha_timeline, so an agent must infer the boundary rather than read it.

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?

It supplies concrete trigger phrasings ('am I manglik', 'is sade sati running', 'do I have kaal sarp dosh') that map cleanly onto user intents, giving a clear use context. There are no explicit when-not conditions or named alternatives for the overlapping full-chart and timeline tools.

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

All VedicDost: Vedic Astrology, Kundli & AI Astrologer tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?