Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_char_antar_dasha

Calculate Char Antar Dasha periods using birth date, time, coordinates, and a Mahadasha sign for Vedic astrology analysis.

Instructions

Execute char_antar_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>"
    },
    "name": "get_char_antar_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 (e.g., Aries, Taurus, Gemini, Cancer, Leo, Virgo, Libra, Scorpio, Sagittarius, Capricorn, Aquarius, Pisces)

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 provided, so the description carries the full burden of behavioral disclosure. It says only to execute an API and does not describe whether the operation is read-only, what it returns, whether it has side effects, or what output an agent should expect.

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?

The description is extremely short and front-loaded, but it is under-specified rather than efficient. The opaque phrase "AstroChalit API" consumes most of the sentence without making the tool's behavior or purpose clearer.

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?

This is a complex tool with 10 parameters, 9 required fields, no annotations, and no output schema. The description does not explain the computation, return value, prerequisites, or relationship to the many sibling dasha tools, leaving it inadequate for correct selection and invocation.

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?

The input schema has 100% description coverage for all 10 parameters, including birth date/time, coordinates, timezone, and mahadasha_sign. The description adds no parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 only restates the tool name as an API invocation: "Execute char_antar_dasha AstroChalit API." It does not explain what Char Antar Dasha is, what the tool computes, or how it differs from sibling dasha tools such as get_char_maha_dasha and get_char_pratyantar_dasha.

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 exclusions, and no mention of the sibling dasha calculation tools. An agent is left to infer the tool's role entirely 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