Skip to main content
Glama

Supastro

Check the doshas in a birth chart

check_doshas
Read-onlyIdempotent

Checks a birth chart for the doshas people are commonly told they have: Manglik (Mangal Dosha), Kaal Sarp, Pitra, Grahan, Guru Chandal, Shrapit and Angarak Dosha, and Sade Sati. For each one it says whether it is formed in this chart, whether a cancellation applies, the chart facts behind that answer, and whether the rule rests on a classical verse or only on a later convention. Use it when someone asks whether they are Manglik, have Kaal Sarp Dosha or another dosha, or whether a dosha they were told about is real or cancelled. Checks all of them unless some are named.

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

Input Schema

NameRequiredDescriptionDefault
doshasNoOptional. Which doshas to check. Leave out to check all of them.
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.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: each dosha answer includes formation status, whether a cancellation applies, the underlying chart facts, and whether the rule rests on a classical verse or a later convention, plus the all-by-default scoping. It does not discuss computation caveats or accuracy limits, so not a 5.

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 verb and scope, then the return content, then the usage trigger. The long dosha enumeration earns its place because it defines coverage and feeds the enum. Minor redundancy between 'Checks all of them unless some are named' and the schema's own note on the doshas parameter.

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 carries the burden of describing return values, and it does so well: per-dosha formation status, cancellation, supporting chart facts, and classical-vs-convention provenance. The inputs are complex, with date ambiguity and coordinate rules, but those are fully covered by the schema. Only missing piece is any note on precision or limitations of the underlying rules.

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%, so every parameter, including the doshas enum and the date/time disambiguation rules, is already documented in the schema. The description only restates the default-to-all behavior of the doshas array, which the schema itself already says. Baseline 3 is correct when the schema does the heavy lifting.

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 ('Checks a birth chart for the doshas') and enumerates the exact eight doshas covered, so the scope is unambiguous. It also names the alternative interpretations it is not ('whether a dosha they were told about is real or cancelled'), letting an agent separate it from chart-casting siblings without opening the schema.

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 an explicit trigger: 'Use it when someone asks whether they are Manglik, have Kaal Sarp Dosha or another dosha.' It also documents the default ('Checks all of them unless some are named'), which removes ambiguity about whether to pass the optional array. It stops short of naming a sibling alternative, such as routing to check_sade_sati or get_sade_sati_lifetime for deeper Sade Sati analysis, so a 4 rather than a 5.

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