Skip to main content
Glama
astroway

astroway-mcp

Official

Dashas — Chara Sookshmadasha

vedic_dashas_chara_sookshma
Read-onlyIdempotent

Calculate 4-level Chara Sookshmadasha sub-dashas to time planetary influences for any target date.

Instructions

Chara Sookshmadasha — 4-level cascade.

[Group: Vedic]

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.
Behavior2/5

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

Annotations indicate readOnly, destructive false, idempotent, but the description only adds '4-level cascade' which is vague. It does not disclose any other behavioral traits beyond annotations.

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 brief but not well-structured. It lacks headings or bullet points, though it is front-loaded with the tool name and example.

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 and the description does not explain what the '4-level cascade' means or what the output contains. For a complex Vedic dasha calculation, the description is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The example request body provides practical context for parameter values, adding value beyond the schema.

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 says 'Chara Sookshmadasha — 4-level cascade' but does not explicitly state that it computes or returns this dasha. It fails to differentiate from sibling tools like vedic_dashas_chara_maha or vedic_dashas_chara_antar, which also compute chara dashas at different levels.

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 tool versus alternatives. With many sibling dashas tools, the description should indicate that this is for the sookshma level of chara dasha, but it does not.

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