Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_divisional_chart_d1

Generate a D1 divisional chart from birth date, time, coordinates, and timezone to obtain Vedic astrology planetary positions for a specific location and moment.

Instructions

Execute d1chart 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_divisional_chart_d1"
  }
}

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
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: not that this is a read-only computation, not whether results are deterministic, not what the response contains, and not the default-timezone behavior that the schema hints at.

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, so nothing is wasted, but the brevity is under-specification rather than conciseness. There is no front-loaded statement of what the tool returns or how to interpret 'd1chart'.

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 9-parameter computation tool with no annotations and no output schema, the description should explain what the returned chart contains and how it relates to the sibling divisional charts. It supplies none of that, leaving an agent unable to predict the result.

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 nine parameters (birth date/time, latitude, longitude, timezone) are already documented in the schema. The description adds no meaning beyond that, which is acceptable under the baseline rule but earns no credit.

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 d1chart AstroChalit API" restates the tool name and an internal API label rather than describing the operation. An agent can infer it produces a D1 (Rashi) divisional chart from the name and siblings, but the description itself supplies no specific verb+resource phrasing and does not distinguish it from the D2/D3/D9 siblings.

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?

There is no when-to-use guidance, no mention of when a D1 chart is preferred over the other divisional charts, and no prerequisites (e.g., birth data required, timezone default). The only signal is 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