Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_vimshottari_maha

Calculate Vimshottari Mahadasha periods from birth date, time, and coordinates to identify planetary period timelines for Vedic astrology analysis.

Instructions

Execute vimshottari_maha 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_vimshottari_maha"
  }
}

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.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 delivers none of it: it does not say the tool is a read-only computation, what it returns, whether a timezone default applies, or whether the call is stateless or rate limited. Calling it an 'AstroChalit API' execution adds no usable behavioral context.

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 a single short phrase with no wasted words, but the brevity comes from under-specification rather than economy, so the sentence does not earn its place.

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?

The tool requires eight mandatory birth parameters and returns an astrological computation, and the definition has no output schema or annotations to fall back on. A five-word API label is not enough for an agent to call this correctly or interpret the result.

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 all nine birth-data parameters, including the timezone default, are already documented in the schema. The description adds no meaning beyond that, so the baseline of 3 applies.

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 as 'Execute vimshottari_maha AstroChalit API,' which only implies a Vimshottari Maha Dasha calculation via an API call. It never says what a 'maha' period is or how it differs from siblings such as get_vimshottari_antar or get_vimshottari_prana, so an agent must already know the domain to distinguish them.

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 prerequisite or exclusion statement, and no reference to any alternative sibling tool. The absence of guidance between the maha/antar/pratyantar/sookshma/prana hierarchy is a real gap here because those siblings differ only by dasha level.

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