Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_divisional_chart_d60

Calculates the D60 (Shashtiamsha) divisional Vedic astrology chart from birth date, time, and geographic coordinates for detailed karmic analysis.

Instructions

Execute d60chart 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_d60"
  }
}

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 supplied, so the description carries the full behavioral burden and discloses nothing. It does not say whether this is a read-only computation, whether results are deterministic, whether the timezone default of Asia/Kolkata silently applies, or what form the returned chart data takes.

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?

Extremely short, but this is under-specification rather than conciseness. The single fragment is not front-loaded with usable information and wastes its only clause on an internal API name.

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 astrological computation with no output schema and no annotations, the description should at minimum state what is computed and what is returned. Neither is present, leaving the agent unable to predict the response shape or validate the call.

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% across all nine parameters, including ranges and the Asia/Kolkata timezone default, so the schema already documents the inputs. The description adds nothing beyond that baseline; it never explains that these are birth-date/time/place coordinates feeding the calculation.

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 d60chart AstroChalit API' only restates the tool name and the vendor API it wraps. It never states that it computes a D60 divisional (Shashtiamsha) Vedic astrology chart from birth data, so the actual verb-plus-resource meaning is left for the agent to infer from the name alone.

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, no mention of how this differs from the ~30 sibling divisional-chart tools (d1 through d601), and no prerequisites such as requiring accurate birth time for fine divisions. The agent gets no signal about which of the sibling charts to select.

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