Skip to main content
Glama
astroway

astroway-mcp

Official

Dashas — Kalachakra Sookshmadasha

vedic_dashas_kalachakra_sookshma
Read-onlyIdempotent

Calculate the four-level Kalachakra Sookshmadasha sub-dasha for a given birth chart and target date to time Vedic astrology events.

Instructions

Kalachakra Sookshmadasha — 4-level cascade.

[Group: Vedic] [Cost: 50 credits (Tier 3)]

Example request body: {"date":"1947-08-15","time":"02:00:00","timezoneOffset":5.5,"latitude":27.49,"longitude":77.67,"targetDate":"2026-05-06"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesBirth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss). Defaults to lat/lon/tz=0 if omitted; pass real values for accurate computation.
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. The description adds the '4-level cascade' context but does not disclose additional behavior (e.g., output format, limitations). No contradictions.

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 description is very short but lacks structure and essential details. It includes an example but no clear statement of purpose or output.

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?

No output schema exists, yet the description does not explain what the tool returns. The example shows only input, leaving the AI to guess the output format and content. Incomplete for a complex dasha tool.

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?

The input schema has extensive descriptions (100% coverage), so the tool description adds no extra parameter meaning. Baseline score is appropriate.

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 merely states 'Kalachakra Sookshmadasha — 4-level cascade' and provides an example, but lacks a clear verb and does not differentiate this tool from numerous sibling dasha tools (e.g., vedic_dashas_kalachakra_maha, antar, etc.).

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 guidance on when to use this specific level of Kalachakra dasha versus other levels (maha, antar, prana, etc.) or alternatives. The description only includes cost and group metadata.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server