Vedic Astrology and Kundli MCP Server by RoxyAPI

Declination Parallels - Planets at same or opposite declination

post_vedic_astrology_parallels

Read-only

Calculate planetary declinations and find parallels (same declination) and contraparallels (opposite declination). Parallels are considered equivalent to conjunctions in strength, contraparallels to oppositions. Returns declination for each planet and all parallel/contraparallel aspects. Declination parallels API, planetary declination calculator, contraparallel aspects.

Input Schema

TableJSON Schema

Name	Required	Description
`orb`	No	Orb in degrees for parallel/contraparallel detection. Defaults to 1.5°.
`date`	Yes	Date in YYYY-MM-DD format. Planetary declinations are calculated for this date to find parallel and contraparallel aspects.
`time`	Yes	Time in HH:MM:SS format (24-hour). Exact time affects declination values, especially for the fast-moving Moon.
`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.
`latitude`	Yes	Observer latitude in decimal degrees. Used for topocentric declination corrections.
`timezone`	No	Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST).
`longitude`	Yes	Observer longitude in decimal degrees. Affects local time context for declination calculations.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`planets`	Yes
`datetime`	Yes
`parallels`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / timezone / description

Previous value: -"Timezone offset from UTC in hours. Defaults to 5.5 (IST)."New value: +"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST)."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "datetime": {
+      "type": "string"
+    },
+    "parallels": {
+      "items": {
+        "properties": {
+          "dec1": {
+            "type": "number"
+          },
+          "dec2": {
+            "type": "number"
+          },
+          "orb": {
+            "type": "number"
+          },
+          "planet1": {
+            "type": "string"
+          },
+          "planet2": {
+            "type": "string"
+          },
+          "type": {
+            "enum": [
+              "parallel",
+              "contraparallel"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet1",
+          "planet2",
+          "type",
+          "orb",
+          "dec1",
+          "dec2"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "planets": {
+      "items": {
+        "properties": {
+          "declination": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "rightAscension": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "declination",
+          "rightAscension"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "datetime",
+    "planets",
+    "parallels"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "date": "2026-02-03",
+    "latitude": 17.385044,
+    "longitude": 78.486671,
+    "time": "12:00:00"
+  }
+]

changedInput schema / properties / compact / description

Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"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."

Changed1 schema field changedJul 22, 2026

changedInput schema / properties / compact / description

Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."

Changed1 schema field changedJul 22, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}

Changed1 schema field changedJul 12, 2026

changedInput schema / properties / timezone / anyOf

Previous value: -[
-  {
-    "maximum": 14,
-    "minimum": -14,
-    "type": "number"
-  },
-  {
-    "pattern": "^[A-Za-z_]+(?:\\/[A-Za-z0-9_+-]+){0,2}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 14,
+    "minimum": -14,
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

First observedJul 8, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that it returns declination for each planet and all parallel/contraparallel aspects, but this is largely covered by the output schema. It does not disclose any side effects or edge cases beyond that, which is acceptable given 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.

Conciseness2/5

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

The first two sentences are concise and informative, but the description ends with keyword-stuffing: 'Declination parallels API, planetary declination calculator, contraparallel aspects.' This is redundant and provides no value to an agent, undermining conciseness and violating the principle that every sentence should earn its place.

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?

The tool has an output schema and full parameter documentation. The description explains the astrological significance (parallels = conjunctions, contraparallels = oppositions), which adds valuable context. It does not mention the monthly sibling, but that is not essential for calling this tool correctly. Overall, it is complete enough for an agent to use.

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 baseline is 3. The description does not add any parameter-specific meaning beyond the schema; it only mentions the general output. Since the schema already documents all parameters thoroughly, this is adequate.

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 the tool's function: calculating planetary declinations and identifying parallels and contraparallels, with a specific resource (planetary declinations) and action (calculate and find). It also explains the astrological significance, making the purpose unambiguous. However, it does not differentiate itself from the sibling tool post_vedic_astrology_parallels_monthly, so it lacks sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that it is for single-date calculations, nor does it contrast with monthly variants or other aspect tools. An agent has to infer usage context from the tool name and sibling list, which is insufficient.

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

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?