Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_char_pratyantar_dasha

Calculate Char Pratyantar Dasha periods from birth date, time, coordinates, and selected Mahadasha and Antardasha signs for Vedic astrology timing analysis.

Instructions

Execute char_pratyantar_dasha 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>",
      "mahadasha_sign": "<mahadasha_sign>",
      "antardasha_sign": "<antardasha_sign>"
    },
    "name": "get_char_pratyantar_dasha"
  }
}

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
mahadasha_signYesSign name for Mahadasha
antardasha_signYesSign name for Antardasha

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether the call is a pure computation or a remote request, whether it is read-only, what the response contains, what the required mahadasha_sign/antardasha_sign constrain, or whether results are cached or rate-limited.

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 shortness here reflects under-specification rather than economy. The single fragment is front-loaded with a name restatement and spends its only unique words on a vendor API label.

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 with 11 parameters, 10 of them required, no annotations, and no output schema, the description must explain what the call produces and what the sign inputs mean. It explains neither, leaving an agent unable to verify it is calling the right dasha level.

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 all 11 parameters documented including ranges and the timezone default, so the schema does the semantic work and the baseline of 3 applies. The description itself contributes no meaning about the astrology-specific parameters such as mahadasha_sign and antardasha_sign.

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?

"Execute char_pratyantar_dasha AstroChalit API" largely restates the tool name and adds only the vendor API reference. It never states that this computes a third-level (pratyantar) Vedic dasha period for a birth chart, so an agent cannot distinguish its output from the maha/antar siblings.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative guidance is given. The catalog contains get_char_antar_dasha, get_char_maha_dasha, and get_vimshottari_pratyantar, and the description gives no basis for choosing among them.

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