Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_varshphal_mudda_antar

Calculates the Mudda Antar period in Varshphal using birth date, time, location, and Maha Dasha input for annual Vedic astrology analysis.

Instructions

Execute varshphal_mudda_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>",
      "mahaDashaInput": "<mahaDashaInput>"
    },
    "name": "get_varshphal_mudda_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
mahaDashaInputYesMaha dasha input name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

D1.7/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 behavioral burden, yet it provides none. It does not disclose whether the call is read-only, what the calculation returns, whether errors occur on invalid coordinates, or any rate/permission constraints.

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 single sentence is technically short, but it is under-specified rather than concise: it front-loads only the endpoint name and offers no actionable structure. Nearly all of the text could be removed without losing meaning.

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 complex astrological computation requiring ten parameters, with no annotations and no output schema, the description is wholly inadequate. It does not explain the required birth data, the role of mahaDashaInput, or what an agent should expect from 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%, with every one of the ten parameters documented in the schema itself, including formats such as timezone defaults and coordinate ranges. The description adds no parameter meaning, but the high schema coverage justifies the baseline score of 3.

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 varshphal_mudda_antar AstroChalit API" merely restates the tool name and names the backend endpoint; it does not explain what the Mudda Antar period calculation produces or how it differs from siblings such as get_varshphal_mudda or get_char_antar_dasha.

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 mention of prerequisites, and no routing to or from alternative dasha/varshphal tools. An agent cannot infer from the description when this specific endpoint is the correct choice.

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