Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_divisional_chart_d4

Calculates a D4 divisional chart (Chaturthamsha) from birth date, time, and coordinates to reveal property, home, and material asset insights in Vedic astrology.

Instructions

Execute d4chart 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_d4"
  }
}

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.1/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 disclosure burden, yet it says nothing about what is returned, whether the call is read-only, whether a birth time and place must be accurate, or how errors surface. 'Execute ... API' reveals only that this is a remote computation call, leaving the mutation/safety profile and response shape opaque.

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 fragment is short but wasteful in the wrong direction: it is under-specified rather than concise, packing the only meaning into unexplained product jargon ('AstroChalit API'). Every word is front-loaded but no word carries informational value for an agent.

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 nine parameters (eight required), no output schema, and no annotations, the definition needs to carry substantial explanatory weight and instead carries none. An agent cannot tell what inputs must be a real birth moment, what a D4 chart means, or what result to expect.

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 per-field descriptions and min/max bounds, so the parameters are already well documented in the schema. The description adds nothing about the birth-time coordinates or the timezone default, so 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 restates the tool name in jargon: 'Execute d4chart AstroChalit API' tells an agent that this is the D4 divisional chart endpoint, but never says what a D4 (Chaturthamsha) chart is or what it computes. It fails to distinguish the tool from the twenty sibling divisional-chart tools beyond the number in the name.

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 guidance on when to choose D4 over D1, D9, or any other divisional chart, nor any prerequisites, exclusions, or alternatives. The only signal is the embedded 'd4' label, which the caller must decode themselves.

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