Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_lalkitab_debts

Calculate Lal Kitab debts from birth date, time, and place coordinates to identify inherited or karmic debt combinations in a Vedic astrology chart.

Instructions

Execute lalkitab_debts 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_lalkitab_debts"
  }
}

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

C2/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, and it discloses nothing. It does not state whether the call is read-only, whether it is deterministic, whether authentication or an API key is needed, rate limits, or what the response looks like. Nothing beyond the function name is conveyed.

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?

The single sentence is free of padding but also free of substance; brevity here reflects under-specification rather than conciseness. There is no front-loaded statement of what the tool returns or when to call it.

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

Completeness2/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 computation tool with no annotations and no output schema, the description leaves the agent unable to predict the output or verify correct invocation. The rich schema covers inputs, but the output shape and behavior remain entirely undisclosed.

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 nine parameters documented (day, month, year, hour, minute, second, latitude, longitude, optional timezone defaulting to Asia/Kolkata), so baseline 3 applies. The description adds no meaning beyond the schema, but none is required.

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?

"Execute lalkitab_debts AstroChalit API" is essentially the tool name restated with a generic verb. It does not say what lalkitab debts are (a Vedic astrology debt/affliction calculation), what the result represents, or how it differs from siblings such as get_lalkitab_chart or get_lalkitab_predictions.

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?

No when-to-use guidance at all: nothing about when a lalkitab debts calculation is appropriate versus the chart or prediction siblings, no prerequisites, no note that birth date/time/place must be known. The only implied usage is the tool name itself.

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