Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_calculate_planet_ingress

Calculates when a planet enters zodiac signs between two dates using AstroChalit, with configurable zodiac system, location, and timezone.

Instructions

Execute calculate_planet_ingress 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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "get_calculate_planet_ingress"
  }
}

Input Schema

NameRequiredDescriptionDefault
planetNoPlanet name (e.g. 'Sun', 'Moon', 'Mars')Sun
zodiacNoZodiac system (e.g. 'Tropical', 'Sidereal')Tropical
endDateYesEnd date in YYYY-MM-DD format (e.g. '2024-12-31')
altitudeNoAltitude in meters
latitudeNoLatitude in decimal degrees
timezoneNoTimezone in IANA format (Default: 'Asia/Kolkata')Asia/Kolkata
longitudeNoLongitude in decimal degrees
startDateYesStart date in YYYY-MM-DD format (e.g. '2024-01-01')
calculationMethodNoCalculation method (e.g. 'Moshier', 'Swiss')Moshier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.1/5.0
Behavior2/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 and discloses almost nothing: it does not confirm the call is side-effect free, does not mention the computed output shape (e.g. ingress dates per planet), and gives no rate-limit or error behavior.

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 the brevity is under-specification rather than efficiency: the single clause spends its words on a vendor name instead of the operation, inputs, or result.

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 9-parameter calculation tool with no annotations and no output schema, the description omits what the result contains, how date ranges are interpreted, and when this endpoint rather than get_planet_ingress is appropriate.

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 the description adds no meaning beyond the schema for the 9 parameters (planet, zodiac, dates, coordinates, timezone, calculationMethod). With the schema fully self-documenting, 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 and appends 'AstroChalit API' without saying what a planet ingress calculation yields or how it differs from the sibling get_planet_ingress. An agent learns only that some API call is being executed.

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 mention of prerequisites, and no differentiation from get_planet_ingress or the ephemeris/dasha tools, so selection must be inferred from the name alone.

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