Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_kp_house_significators

Calculate KP house significators from birth date, time, and coordinates to identify planetary rulers for each house in Vedic astrology analysis.

Instructions

Execute kp_house_significators 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_kp_house_significators"
  }
}

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

D1.7/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing: not whether the call is read-only, whether results are computed or cached, whether the timezone default applies, or what a response contains. 'Execute ... API' is a restatement, not a behavioral disclosure.

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 short here means under-specified rather than efficient. There is a single fragment with no structure, no statement of output, and no front-loaded explanation of what a 'house significator' result is.

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 an 8-required-parameter domain-specific calculation tool with zero annotations and no output schema, the description supplies none of the context an agent needs — no definition of KP house significators, no output shape hint, no indication of which sibling to prefer for related queries.

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 all 9 parameters documented (ranges, birth-moment semantics, timezone default), so the baseline is 3 even though the description adds nothing. The description does not compensate for anything, but nothing is left undocumented in the schema either.

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 only restates the tool name with a generic verb ('Execute kp_house_significators AstroChalit API'). It never explains that it returns KP (Krishnamurti Paddhati) house significators for a birth moment, nor how that differs from siblings like get_kp_planet_significators or get_kp_house_cups.

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 (birth date/time/coordinates), and no routing to or away from any of the ~30 sibling astrology tools. An agent must guess entirely from the name.

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