Skip to main content
Glama

Vedic Astrology and Kundli MCP Server by RoxyAPI

Daily Reading - Composed Gochara, Panchanga and Dasha for one native on one day

post_vedic_astrology_daily
Read-only

The composed Vedic daily reading for one native on one date, in one call. Runs classical Gochara as the gate pipeline the texts describe: the house each transiting graha makes from the natal Moon (Janma Rashi), the vedha pair that can cancel it, the Ashtakavarga bindu gate that decides whether it is delivered, and the Phaladeepika XXVI.30 to XXVI.32 nullifiers, so every graha lands in ONE cited state rather than a bar of a chart. Joined to the panchanga day, which runs sunrise to sunrise with a validity window on every limb, plus tarabala and chandrabala resolved for THIS native as windows rather than as one value, the running Vimshottari chain three levels deep, and a KP finance net over the wealth and loss houses. Ships a hand-reproducible strength score with its arithmetic published in the field itself, and states plainly which part is classical and which part is our convention. Positions are computed in the Lahiri sidereal frame; the KP significators behind the finance area use the KP-Newcomb frame, as they do on every KP route. Vedic daily horoscope API, gochara API, daily panchang prediction, tarabala and chandrabala API, ashtakavarga transit strength.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoCivil date to read, in YYYY-MM-DD format. Defaults to today (UTC). The panchanga day it names runs from sunrise at the birth coordinates to the next sunrise, not from midnight, so a reading for this date covers the night that follows it.
langNoResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.en
focusNoWhich signification vocabulary the houseThemes map returns. "general" gives the classical bhava significations (self, wealth, siblings, home, and so on). "finance" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use "finance" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to "general".general
compactNoSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
latitudeYesBirth location latitude in decimal degrees. Sets the natal house cusps behind the Ashtakavarga scorecard and the KP significators, and the sunrise that opens the panchanga day.
nodeTypeNoLunar node type for Rahu and Ketu. "mean" uses the smooth mean node, which is the traditional Vedic default and what printed panchangs use. "true" uses the osculating node, which swings up to 1.5 degrees either side of mean and can therefore move a node into a different rashi and change its gochara house. Defaults to "mean".mean
timezoneNoTimezone: IANA name (e.g. "Asia/Kolkata", "America/New_York") OR decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). IANA strings are resolved to the DST-correct offset for the date being read. Interprets the birth time and the civil date below. Defaults to 5.5.
birthDateYesBirth date in YYYY-MM-DD format. Fixes the Janma Rashi and Janma Nakshatra every part of this reading is counted from, and the natal Ashtakavarga the bindu gate reads.
birthTimeYesBirth time in HH:MM:SS format (24-hour). The Moon moves about half a degree an hour, so an error here moves the Janma Rashi and Janma Nakshatra and therefore every gochara house count, the tarabala and the chandrabala in this response.
longitudeYesBirth location longitude in decimal degrees. Affects local sidereal time for the natal cusps and the sunrise the reading is composed at.

TDQS

A4.2/5.0
Behavior5/5

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

The annotations only supply readOnlyHint=true and destructiveHint=false, so the description carries the behavioral burden. It does this very well by disclosing the classical vs. conventional parts, the hand-reproducible strength score with published arithmetic, sunrise-to-sunrise panchanga days, and the important frame distinction between Lahiri and KP-Newcomb. There is no contradiction with the 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 dense and informative, but it is a single long, sprawling paragraph with a trailing keyword list such as 'Vedic daily horoscope API, gochara API, daily panchang prediction', which adds little value after the main explanation. The front-loaded first sentence is strong, but a tighter structure with shorter sentences or bullets would earn the length.

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 complex tool with 10 parameters, richer annotations would be possible, but no output schema exists. The description still tells an agent what the result includes: a composed gochara/pAnchanga/dasha reading, KP finance values for finance focus, a reproducible strength score, and explicit computational frame notes. It does not enumerate the response fields, but the agent has enough to select the call correctly and infer the general shape.

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%, with each of the 10 parameters fully described in the input schema, so parameter semantics is already handled. The description adds no new parametric details, but it does not need to; the baseline 3 is appropriate because the description reinforces overarching context like 'one native on one date' without duplicating the schema.

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

Purpose5/5

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

The description states a specific resource and action: a composed Vedic daily reading for one native on one date, combining Gochara, Panchanga, and Dasha in one call. It differentiates the tool from its many siblings by emphasizing the single composite call and the 'ONE cited state' behavior, rather than a raw chart bar.

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?

The intended context is clear: use this tool when a single-day, single-native reading that composes gochara, panchanga, dasha, tarabala/chandrabala, and KP finance is needed. The 'in one call' framing implies a contrast with more granular sibling endpoints, though it never explicitly names alternatives or when-not-to-use, so it stays just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Many tools have overlapping concepts (multiple dasha levels, monthly variants, aspects, transit), but detailed descriptions clarify each one's distinct purpose. Still, a few pairs like planetary_positions vs birth_chart or aspects_monthly vs aspects_lunar could confuse an agent initially.

Naming Consistency5/5

All tools follow a strict get_vedic_astrology_* or post_vedic_astrology_* prefix with snake_case resource names. The pattern is predictable and uniformly applied, including the hierarchical dasha drill-downs, making it easy to infer tool families.

Tool Count1/5

With 50 tools, the server is extremely heavy. Many are monthly, interval, or sub-level variants that could be parameterized or consolidated, making the set feel bloated and difficult to navigate for an agent.

Completeness5/5

The tool set covers nearly the entire Vedic astrology domain: reference data (nakshatras, rashis, yoga glossary), core charts (birth, navamsa, divisional), dasha hierarchy, transits, compatibility, doshas, panchang, KP system, and advanced calculations like Shadbala and Ashtakavarga. No significant gaps are apparent.

Resources