Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_kaalsarp_dosha

Determine Kaal Sarp Dosha presence using birth date, time, latitude, and longitude coordinates for Vedic astrology analysis.

Instructions

Execute kaalSarp_dosha AstroChalit API

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": {
      "day": "<day>",
      "month": "<month>",
      "year": "<year>",
      "hour": "<hour>",
      "minute": "<minute>",
      "second": "<second>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_kaalsarp_dosha"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesDay of birth
hourYesHour of birth (0-23)
yearYesYear of birth (e.g., 1990)
monthYesMonth of birth (1-12)
minuteYesMinute of birth (0-59)
secondYesSecond of birth (0-59)
latitudeYesLatitude of birth place
timezoneNoTimezone of birth place (e.g. Asia/Kolkata). Defaults to Asia/Kolkata
longitudeYesLongitude of birth place

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are provided, so the description bears the full behavioral burden, yet it discloses nothing about whether the call is read-only, cost/latency, accuracy caveats, or what the computation returns. Only the endpoint name is conveyed.

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

Conciseness2/5

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

It is short, but that brevity reflects under-specification rather than economy; 'Execute kaalSarp_dosha AstroChalit API' is a bare restatement with no front-loaded purpose or scope. There is no wasted text because there is almost no text.

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

Completeness1/5

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

For a tool taking nine parameters (eight required) with no annotations and no output schema, the description should explain the input contract, the nature of the result, and its relationship to sibling dosha tools. None of that is present, leaving the definition inadequate for correct selection or invocation.

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% and each of the nine parameters has its own description and range constraints, so semantic meaning is fully carried by the schema. The description adds nothing beyond that, which matches the baseline of 3.

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

Purpose2/5

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

The description restates the tool name with the word 'Execute' and appends 'AstroChalit API'; it adds no explanation of what a Kaal Sarp dosha result is or how it differs from the sibling dosha tools. An agent can only guess from the name that it computes a Vedic astrology dosha assessment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of the sibling dosha tools (manglik, pitru, sadesati) that an agent must choose between. Nothing indicates the required birth data context beyond what the schema forces.

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

Deploy Server

Other Tools