Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_lalkitab_chart

Generate a Lal Kitab chart from birth date, time, and location coordinates. Use it to retrieve Vedic astrology Lal Kitab chart data for a person through the AstroChalit API.

Instructions

Execute lalkitab_chart 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_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

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 indication of whether the call is a safe read, whether results are computed or cached, what permissions or rate limits apply, or what the response contains. 'Execute ... API' is a generic wrapper phrase that adds zero behavioral context.

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 its brevity reflects under-specification rather than conciseness. It is not front-loaded with anything actionable for an agent deciding how to call the tool.

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?

This is a 9-parameter tool with 8 required inputs, no annotations, and no output schema, so the description must compensate for all behavioral and return-value unknowns. Instead it says nothing about the chart produced, its format, or how to interpret results, leaving the agent with only the schema.

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 eight required parameters (day, month, year, hour, minute, second, latitude, longitude) plus the optional timezone are already documented with ranges and examples. The description adds no meaning beyond that, which is acceptable at full coverage but not a contribution.

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 ('lalkitab_chart') and adds only 'Execute ... AstroChalit API', which tells the agent nothing about what the tool actually returns or computes. It does not distinguish this chart from siblings like get_lalkitab_predictions or get_lalkitab_debts beyond 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 guidance on when to use this tool, when not to, or which sibling chart tool to pick instead. With ~30 sibling chart tools available, the agent has to guess from the name alone.

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