Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_moon_chart

Calculate a Chandra Kundli with the natal Moon in the 1st house to assess mental peace, emotional stability, subconscious patterns, and Gochar transits from birth details.

Instructions

Calculate Chandra Kundli (Moon Chart) where the natal Moon is positioned in the 1st House (Ascendant), analyzing mental peace, emotional stability, subconscious patterns, and Gochar transits

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_moon_chart"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full behavioral burden; it does disclose that the tool computes a chart and what it analyzes, implying a read-only calculation. It does not state whether the calculation is deterministic, what inputs are mandatory versus defaulted (timezone default is only in the schema), or anything about the response shape.

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 that leads with the computation and then qualifies it with the analysis domains. The list of themes is slightly padded but plausibly useful for matching user intent.

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 nine-parameter computation tool with no annotations and no output schema, the description explains what is computed but not what comes back or how to interpret it. The input side is fully covered by the schema, so the remaining gap is return-value context.

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%, so all nine parameters, including ranges and the timezone default, are already documented in the schema. The description adds no meaning about birth data, coordinate conventions, or timezone handling beyond that baseline, so a 3 is appropriate.

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?

Names a specific verb and resource ('Calculate Chandra Kundli (Moon Chart)') and defines the chart's defining condition (natal Moon in the 1st House), which tells an agent this is the Moon-centered chart rather than the Sun chart. It stops short of naming any sibling explicitly, so differentiation is inferred from the resource name alone.

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?

The description lists interpretive themes (mental peace, emotional stability, subconscious patterns, Gochar transits) but never states when to choose this tool over get_sun_chart or the many get_divisional_chart_* siblings, nor any prerequisites or exclusions. An agent must guess the routing.

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