Vedic Astrology and Kundli MCP Server by RoxyAPI

Get KP planets at time intervals

post_vedic_astrology_kp_planets_interval

Read-only

Calculate positions of all 9 planets (Sun through Saturn, Rahu, Ketu) at regular time intervals with full KP hierarchy: sign lord, star lord, sublord, and sub-sublord. Returns longitude, zodiac sign, nakshatra, sublord, sub-sublord, and KP number (1-249) for each planet at each timestamp. Ideal for tracking planetary motion, finding optimal muhurta windows, analyzing transit patterns, and building KP ephemeris tables. Maximum range of 7 days with 15-minute to 24-hour intervals.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`compact`	No	Set 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.
`ayanamsa`	No	Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. "lahiri" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to "kp-newcomb".	kp-newcomb
`latitude`	Yes	Observer latitude in decimal degrees (for future Lagna calculations)
`nodeType`	No	Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to "mean".	mean
`timezone`	No	IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset for the startDatetime date. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Defaults to 0 (UTC).
`longitude`	Yes	Observer longitude in decimal degrees (for future Lagna calculations)
`endDatetime`	Yes	End datetime in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Maximum 7 days from start. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.
`startDatetime`	Yes	Start datetime in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.
`intervalMinutes`	Yes	Time between calculations in minutes. Range: 15 (quarter-hourly) to 1440 (daily).

TDQS

A4.8/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, confirming safe read operation. The description adds behavioral context: it returns positions for all 9 specific planets (Sun through Saturn, Rahu, Ketu) with full KP hierarchy fields (sign lord, star lord, sublord, sub-sublord, longitude, zodiac sign, nakshatra, KP number). It does not mention pagination (likely not needed given 7-day max) or output format details, but for a read-only tool the disclosure is strong. The only gap is no mention of error behavior for invalid date ranges or timezone handling edge cases.

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

Conciseness5/5

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

Four sentences, each earning its place: 1) what it returns, 2) the specific fields, 3) use cases, 4) constraints. Zero fluff. The most critical operational detail (7-day max, interval range) is front-loaded in the description after the purpose. Perfectly sized for a single paragraph with no redundancy.

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

Completeness5/5

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

Given the 9 parameters (100% schema coverage) and no output schema, the description compensates well by listing the return fields (longitude, zodiac sign, nakshatra, sublord, sub-sublord, KP number) and the planets covered. The sibling list shows this is one of many KP interval tools; the description differentiates clearly by specifying this returns planetary motion at intervals (vs kp_ruling_planets_interval which returns ruling planets at intervals). No output schema is a minor gap, but the description is sufficiently complete for an agent to understand what will be returned.

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

Parameters5/5

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

Schema coverage is 100% with rich descriptions on all 9 parameters. The description further clarifies the role of latitude/longitude ('for future Lagna calculations'), the meaning of ayanamsa options (with domain knowledge like 'kp-newcomb is the most common choice for KP astrology'), and the nodeType distinction (mean vs true). The start/end datetime description explains timezone handling in detail. This adds significant value beyond the schema alone.

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 clearly states it calculates positions of all 9 planets at regular time intervals with full KP hierarchy, distinguishing it from sibling tools like get_vedic_astrology_kp_planets (likely a single-point snapshot) and post_vedic_astrology_kp_rasi_changes (which focuses on sign boundary crossings). The verb 'calculate' and resource 'planetary positions with KP hierarchy at intervals' is specific and unambiguous.

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

Usage Guidelines5/5

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

The description explicitly states the ideal use cases: 'tracking planetary motion, finding optimal muhurta windows, analyzing transit patterns, and building KP ephemeris tables.' It also provides critical constraints: 'Maximum range of 7 days with 15-minute to 24-hour intervals.' This clearly guides when to use this tool versus alternatives like post_vedic_astrology_planetary_positions (which likely provides a single timestamp) or post_vedic_astrology_kp_horary (for single moment horary analysis).

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

All Vedic Astrology and Kundli MCP Server by RoxyAPI tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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

Need Help?