AstroWay Divination and esoterica

Vedic Divisional Chart (DEPRECATED: use /vedic/varga/{D}<*>)

astroway_specialized_vedic_divisional

Read-onlyIdempotent

DEPRECATED: moved to dedicated per-varga endpoints /vedic/varga/{D1..D60} for OpenAPI/SDK ergonomics. This generic endpoint still works and stays live until its 2027-06-15 sunset (12-month, per the /v1 stability policy), then will be removed; migrate to /vedic/varga/{D}. Calculate a Vedic divisional (varga) chart using sidereal zodiac. Supported vargas: D1–D60 (e.g. D9 Navamsha).

[Group: Specialized Charts] [Endpoint: POST /v1/vedic-divisional] [Cost: 20 credits (Tier 2)] [⚠️ DEPRECATED — will be removed in a future API version. Avoid using.]

Input Schema

Name	Required	Description
`body`	Yes	Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as "Placidus" is refused, and the case matters because I and i are two different Sunshine systems.
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

Name	Required	Description	Default
`varga`	No
`planets`	No
`ayanamsa`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the deprecation timeline and endpoint cost, but does not disclose return format, pagination, or error behavior beyond what annotations provide.

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 deprecation notice, then states the core purpose. It includes metadata tags ([Group], [Endpoint], [Cost]) that are informative but not part of the natural description flow. Overall efficient with no wasted sentences.

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

Completeness4/5

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

For a deprecated read-only calculation tool with a rich input schema and an output schema, the description covers migration, cost, and core function. It could mention what the output includes, but the output schema likely handles that.

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%, so the schema fully documents parameters including nested body fields, timezone, ayanamsa, etc. The description mentions 'sidereal zodiac' and supported vargas but adds no syntax or format details beyond what the schema provides.

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?

The description clearly states it calculates a Vedic divisional (varga) chart using sidereal zodiac and lists supported vargas (D1–D60). However, it does not explicitly distinguish itself from sibling tools like astroway_specialized_draconic or astroway_specialized_harmonics beyond the opening deprecation notice.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It provides a clear migration path to `/vedic/varga/{D1..D60}` and states the sunset date, which tells the agent when to use the new endpoints. It lacks explicit guidance on when to choose this deprecated endpoint over the alternative, but the deprecation notice strongly implies avoidance.

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

All AstroWay Divination and esoterica tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?