Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_planetary_position

Calculate planetary positions for a birth date, time, and location using latitude, longitude, and timezone via the AstroChalit API. Use the results for Vedic astrology charts and horoscope analysis.

Instructions

Execute planetary_position 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_planetary_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesDay of birth
hourYesHour of birth (0-23)
nameNoPerson's nameUser
yearYesYear of birth (e.g., 1990)
monthYesMonth of birth (1-12)
placeNoBirth placeDelhi, India
genderNoGender of personMale
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?

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing: no auth requirements, no rate limits, no note on whether the call is a pure read, and no hint about response shape or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is compact with no filler, but brevity here is achieved by omission rather than by editing: there is nothing front-loaded because there is nothing substantive to front-load.

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?

For a 12-parameter tool with eight required fields, no annotations, and no output schema, the definition should explain what is computed from those birth details and roughly what comes back. The one-line description leaves all of that unaddressed.

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 every one of the 12 parameters (day, month, year, hour, minute, second, latitude, longitude, name, place, gender, timezone) is documented in the schema itself. The description adds no syntax, format, or defaulting nuance, 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 planetary_position AstroChalit API" mostly restates the tool name and the backend it wraps. The token "planetary_position" faintly signals a subject area, but the description never says what the tool actually returns (planet longitudes? signs? houses?) nor how it differs from siblings such as get_calculate_ephemeris or get_calculate_planet_ingress.

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 prerequisites, and no mention of any alternative. With at least three siblings plausibly overlapping planetary calculations, the agent is given nothing to route on.

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