Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_vimshottari_pratyantar

Calculate Vimshottari Pratyantar Dasha periods from birth details and selected Maha/Antar Dasha planets to pinpoint sub-period timing.

Instructions

Execute vimshottari_pratyantar 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": "<mahaDasha>",
      "antarDasha": "<antarDasha>"
    },
    "name": "get_vimshottari_pratyantar"
  }
}

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
mahaDashaYesPlanet name for Maha Dasha
antarDashaYesPlanet name for Antar Dasha

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?

With no annotations supplied, the description carries the full behavioral burden and discloses essentially nothing. It does not state that this is a read-only computed lookup, whether it calls an external service with latency or rate limits, whether the mahaDasha/antarDasha values must correspond to a valid planetary sequence, or what the response contains.

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 the brevity comes from under-specification rather than economy: seven words that convey no scope, inputs, or output. There is no front-loaded statement of what the call produces.

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?

An 11-parameter tool requiring 10 fields, with no annotations and no output schema, needs a description that explains the dasha hierarchy, valid planet values, and the return shape. The single sentence supplies none of that and leaves the agent unable to call it correctly without external knowledge.

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 every one of the 11 parameters documented inline (including ranges for day/month/year/hour/minute/second and lat/long bounds), so the schema already carries the parameter burden. Baseline 3 applies; the description adds no extra meaning, such as expected planet-name spellings for mahaDasha/antarDasha or the timezone default.

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 "Execute vimshottari_pratyantar AstroChalit API" merely restates the tool name plus the vendor name. It never says what a pratyantar dasha is, what the tool returns, or how it differs from the antar/maha/prana/sookshma siblings. An agent learns nothing beyond what the name already conveys.

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?

There is no when-to-use guidance, no mention of prerequisites (birth date/time/coordinates plus an existing mahaDasha and antarDasha selection), and no routing to alternatives such as get_vimshottari_antar or get_vimshottari_prana. The definition does not mislead, but it offers nothing to select on.

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