Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_kp_planet_significators

Calculates KP planet significators from birth date, time, and location to support Vedic astrology chart analysis.

Instructions

Execute kp_planet_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_planet_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 burden of behavioral disclosure, and it discloses nothing: no auth requirements, no statement that it is a pure read/lookup, no cost or rate-limit hints, and no indication of what the response contains. For an unannotated API-call tool this is a complete gap.

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 by omission rather than by efficiency: a single fragment that names the endpoint without front-loading any actionable information. Length is not the problem; the absence of substance 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?

With 9 parameters (8 required), no annotations, and no output schema, the description needed to explain the domain concept, the required birth-data inputs, and what comes back. It provides none of that, leaving an agent unable to determine correct use beyond the raw schema constraints.

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?

All 9 parameters have schema descriptions at 100% coverage (birth date/time components, lat/long, and a documented timezone default of Asia/Kolkata), so the schema does the work here. The description adds no syntax, range, or defaulting context beyond what the schema already states; 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?

The description says only "Execute kp_planet_significators AstroChalit API", which essentially restates the tool name plus the backend it hits. It never states what a 'planet significator' result actually is (KP astrology significator sets) or how it differs from close siblings like get_kp_significators or get_kp_house_significators.

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 tool. An agent cannot tell from this text whether to call this versus get_kp_significators or get_kp_birth, both of which are in the sibling list.

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