Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_divisional_chart_d8

Generate a D8 divisional chart from birth date, time, and coordinates to analyze Ashtamsha planetary placements in Vedic astrology.

Instructions

Execute d8chart 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_d8"
  }
}

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.7/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 burden, yet it discloses nothing about read-only vs mutating behavior, cost, rate limits, or whether computation happens server-side. A single imperative sentence gives an agent no behavioral signal at all.

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 text is short but not concise in the useful sense: it is under-specified rather than economical, and the opaque token "d8chart AstroChalit API" is not front-loaded with any actionable information.

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 tool with no annotations and no output schema, the description explains neither the returned chart structure nor the meaning of the d8 division. Nothing an agent needs in order to interpret or trust the result is present.

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% and every one of the nine birth-data parameters is documented with ranges and examples in the schema itself. The description adds no parameter meaning beyond that, but with full schema coverage the baseline of 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 d8chart AstroChalit API" restates the tool name with an opaque product token. It never says what a d8 divisional chart is, what information it returns, or how it differs from the 19 sibling d1/d2/d3...d601 chart tools beyond the number embedded 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 Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no when-not-to-use, and no named alternative such as get_divisional_chart_d1 or get_divisional_chart_d9. The agent must already know Vedic astrology divisional charts to pick this tool correctly.

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