Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Varga D40: Khavedamsa

astroway_vedic_varga_d40
Read-onlyIdempotent

Generate a Khavedamsa (D40) Vedic divisional chart to assess auspicious and inauspicious effects linked to maternal lineage from birth date, time, latitude, and longitude.

Instructions

Khavedamsa chart (auspicious & inauspicious effects, maternal lineage).

[Group: Vedic] [Endpoint: POST /v1/vedic/varga/D40] [Required: date, time, latitude, longitude] [Cost: 20 credits (Tier 2)]

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
cosmogramNo
longitudeYes
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
nameNo
lagnaNo
vargaNo
planetsNo
ayanamsaNo
julianDayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world). The description adds genuinely useful operational facts: endpoint, 20-credit Tier 2 cost, and the required input set. It says nothing about what ayanamsa/house system choices do to results, which matters for a calculation tool.

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

Conciseness4/5

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

Front-loads the chart identity and meaning, then uses compact tagged lines for group, endpoint, requirements, and cost. No wasted prose; the bracketed format is slightly mechanical but scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema and annotations exist, so return values and safety need not be explained. However, with 13 parameters and only 23% coverage, an agent still lacks guidance on the optional astronomical settings and on which varga tool to pick, leaving real gaps.

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

Parameters2/5

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

Schema description coverage is only 23% across 13 parameters, and the description merely restates the four required fields. Undocumented parameters (city, name, cosmogram, zodiacType, houseSystem, ayanamsaId) get no explanation, so the text does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific chart (Khavedamsa / D40) and its interpretive domain (auspicious & inauspicious effects, maternal lineage), which distinguishes it from the D1/D9/D45 siblings by name. It does not say what the call actually returns or how it differs conceptually from other divisional charts, but the verb+resource is identifiable.

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 or when-not-to-use guidance and no mention of alternatives among the many varga tools. Only the required-parameter list is given, which the schema already enforces.

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