Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_vimshottari_antar

Calculate Vimshottari Antardasha sub-periods using birth details and a selected Maha Dasha planet for Vedic astrology analysis.

Instructions

Execute vimshottari_antar 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>"
    },
    "name": "get_vimshottari_antar"
  }
}

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 (e.g., Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury, Ketu, Venus)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

D1.8/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: not whether the call is read-only, whether it requires an API key or account, what happens with invalid birth data, or whether results are cached. One sentence of naming convention is all that is provided.

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 brevity here comes from under-specification rather than economy. The single phrase is not front-loaded with a verb-plus-resource statement an agent can act on.

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

Completeness2/5

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

This is a 10-parameter tool with 9 required inputs and no output schema, so the description should explain at minimum what the response contains (the antar dasha lord and its date boundaries). It provides none of that, leaving the agent to guess the return shape entirely.

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 10 parameters carries a clear description, including ranges and the timezone default, so the schema does the heavy lifting. The description adds no extra meaning, such as how mahaDasha interacts with the birth date to select the antar period, which is the one semantic the schema does not explain.

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 vimshottari_antar AstroChalit API" mostly restates the tool name and the underlying API label. It implies computing an antar dasha, but never states what an antar dasha result is or how it differs from the sibling tools get_vimshottari_maha, get_vimshottari_pratyantar, or get_vimshottari_prana.

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 prerequisite information, and no mention of the sibling dasha-level tools that would be the natural alternatives. The agent must infer the tool's role purely from its name.

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