Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_vimshottari_sookshma

Calculate Vimshottari Sookshma Dasha periods from birth date, time, location, and selected Maha, Antar, and Pratyantar Dashas for precise Vedic astrology timing.

Instructions

Execute vimshottari_sookshma 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>",
      "pratyantarDasha": "<pratyantarDasha>"
    },
    "name": "get_vimshottari_sookshma"
  }
}

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
pratyantarDashaYesPlanet name for Pratyantar 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 disclosure burden and discloses nothing: no statement of read-only vs mutating behavior, no return shape, no auth or rate-limit notes. "Execute ... API" is a bare label and tells an agent nothing about what happens on invocation.

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 is under-specification rather than concision; the single phrase is not front-loaded with any actionable information. Nothing in the sentence earns its place beyond repeating the function name.

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 12-parameter, 11-required tool with no annotations and no output schema, the description should at minimum explain the dasha hierarchy inputs and expected response. It does none of that, leaving the agent to infer everything from parameter names.

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 12 parameters (birth date/time, latitude/longitude, timezone, and the three dasha level planet names) are already documented in the schema. The description adds no extra meaning such as valid planet spellings or how the three dasha levels must nest, so the baseline 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?

"Execute vimshottari_sookshma AstroChalit API" mostly restates the tool name and the vendor; it never says what a sookshma dasha is or what the call returns. The only differentiation from siblings like get_vimshottari_antar or get_vimshottari_prana comes from the name token itself, not from the prose.

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 at all: nothing says to pick this over the antar/pratyantar/prana dasha siblings, nor what inputs must already be known. The one implied hint is that mahaDasha, antarDasha and pratyantarDasha are required, but the description never states that dependency.

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