Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_kp_house_cups

Calculate KP house cusps for a birth chart using birth date, time, latitude, and longitude. Use it to get Krishnamurti Paddhati house divisions needed for KP astrology analysis.

Instructions

Execute kp_house_cups 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_cups"
  }
}

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.9/5.0
Behavior2/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 and discloses almost nothing: it does not say whether this is a pure computation, whether results depend on an external ephemeris service, whether errors occur for invalid dates, or what the response contains. Only the generic word 'Execute' hints that it is a call-through to a remote API.

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 a single short phrase, but the brevity comes from under-specification rather than efficiency: there is no front-loaded statement of what the tool computes or returns. Nothing is wasted, but almost nothing is conveyed.

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 nine-parameter, eight-required astrological computation with no annotations and no output schema, the description supplies none of the context an agent needs. The agent cannot know what a 'house cup' is, what the return shape is, or when this tool is the correct choice.

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 every one of the nine parameters (birth date/time components, latitude, longitude, timezone) is documented in the schema with ranges and units. The description adds no meaning beyond that, which is the baseline case when the schema already does the work.

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 with the vendor tag ('Execute kp_house_cups AstroChalit API') and never explains what 'kp_house_cups' produces or means. It says nothing that would let an agent distinguish it from siblings like get_kp_planets or get_kp_house_significators, so its purpose is only identifiable from the name itself.

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, no exclusions, and no mention of any alternative tool. The agent is left to infer from the function name alone that this is a KP house-cusp calculation.

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