Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_divisional_chart_d27

Calculate a D27 divisional Vedic astrology chart from birth date, time, coordinates, and timezone to analyze subtle planetary influences.

Instructions

Execute d27chart 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_d27"
  }
}

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 supplied, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only, not whether it makes an external network request despite the word 'Execute', not what permissions or defaults apply (e.g. timezone defaulting to Asia/Kolkata), and not what the response contains. 'Execute ... API' is the only hint and it is ambiguous.

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 six-word sentence is short but under-specified rather than concise; there is no front-loaded statement of outcome, no structure, and the vendor jargon 'd27chart AstroChalit API' consumes the only space available for meaning.

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 tool with nine parameters, eight required, no annotations, and no output schema, the description supplies nothing about what is returned (chart data structure, house/planet positions, error cases) or the operational characteristics of the external API call. It is wholly inadequate for the tool's complexity.

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 every birth-data field (day, month, year, hour, minute, second, latitude, longitude, timezone) documented inline, so the description does not need to restate them. It adds nothing beyond the schema, but the baseline of 3 applies when the schema 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 'Execute d27chart AstroChalit API' is essentially a restatement of the tool name with an opaque vendor token; the only reason it is interpretable at all is that the name and siblings reveal it is a divisional (D27) chart computation. It never says what a D27 chart is or that it computes a Vedic astrology divisional chart from birth data.

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 exclusions, and no mention of how this differs from the other twenty divisional chart tools (d1 through d601) or from get_lalkitab_chart. An agent must infer entirely from the tool name that the numeric suffix selects the divisional chart.

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