Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_divisional_chart_d601

Calculates the D601 divisional chart from birth date, time, latitude, and longitude to support detailed Vedic astrology chart analysis.

Instructions

Execute d601chart 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_d601"
  }
}

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
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, yet it discloses nothing: not whether the call is read-only or mutating, not whether it is deterministic or costly, not what the timezone default means for results, and not what the response contains. "Execute ... API" conveys zero behavioral traits beyond the bare fact that a call is made.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short and wastes no words, but that is brevity through omission rather than efficient communication. There is no front-loaded statement of what the tool returns or when it applies.

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?

This is a complex tool: eight required parameters describing an exact birth moment and place, no output schema, and no annotations. Against that complexity the description supplies nothing about the computed result or its interpretation, leaving an agent unable to judge whether the output is what it needs.

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 one of the nine parameters (day, month, year, hour, minute, second, latitude, longitude, timezone) individually documented including ranges and an example timezone default. The description adds nothing beyond the schema, so the 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?

"Execute d601chart AstroChalit API" essentially restates the tool name plus the vendor API name. It never says what a d601 divisional chart is, what it computes, or how it differs from the twenty-plus sibling divisional-chart tools (d1, d10, d60, etc.). An agent learns only that some API call happens.

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 statement, no prerequisite (e.g., that birth date/time/place must be known), and no routing hint among the many sibling chart tools. The only implicit signal is the name itself, which the agent must decode on its own.

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