Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_planet_ingress

Retrieve planetary ingress dates for a selected month and year, showing when planets enter zodiac signs under Vedic or Western systems, with optional filtering by planet.

Instructions

Execute planet_ingress AstroChalit API to get transit/ingress of planets into zodiac signs

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": {
      "month": "<month>",
      "year": "<year>"
    },
    "name": "get_planet_ingress"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYear (2024 to 2040 available)
monthYesMonth (1-12)
planetNoPlanet name or 'All' to get all planetary ingresses (Default: 'All')All
zodiacSystemNoZodiac system: 'Vedic' (Sidereal) or 'Western' (Tropical). Default: 'Vedic'Vedic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/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 of behavioral disclosure. It does not state whether results are a list of dated events, whether the year range is enforced, pagination, or any auth/rate-limit characteristics — 'Execute ... API' hints at a thin wrapper without saying what that implies.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the phrase 'Execute ... AstroChalit API' is mildly redundant but does signal that this is a backend-wrapper call. Nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter query tool with no output schema and no annotations, the description is minimally adequate — the schema covers inputs well. It is incomplete in that it never clarifies the return shape or its relationship to the near-identically named calculation sibling.

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 coverage is 100%: year bounds, month range, the planet enum with 'All' default, and the Vedic/Western zodiac option are all documented in the schema itself. The description adds no meaning beyond those fields, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb-plus-resource: retrieve transit/ingress events of planets entering zodiac signs. That is clearly distinct from chart or dasha siblings, though it does not explain how it differs from the similarly named 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus get_calculate_planet_ingress or the ephemeris tool. The only implied context is that the caller wants ingress dates, which is left for the agent to infer.

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