AstroWay Psychological astrology

Rudhyar: Transits as Rebirth

astroway_psyr_transits_as_rebirth

Read-onlyIdempotent

Reframe major transits as rebirth.

[Group: Modern Psychological] [Endpoint: POST /v1/modern/rudhyar/transits-as-rebirth] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]

(Cursor-friendly alias for astroway_psychological_modern_rudhyar_transits_as_rebirth.)

Input Schema

Name	Required	Description	Default
`city`	No
`date`	Yes
`name`	No
`time`	Yes
`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.
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`latitude`	Yes
`timezone`	No	IANA 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.
`cosmogram`	No
`longitude`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`ayanamsaId`	No
`zodiacType`	No
`houseSystem`	No		P
`timezoneOffset`	No	Hours 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

Name	Required	Description	Default
`source`	No
`doctrine`	No
`disclaimer`	No
`rebirthThemes`	No
`natalRebirthSignatures`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 7, 2026

removedInput schema / properties / ayanamsaId / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / ayanamsaId / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / disclaimer / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / disclaimer / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / doctrine / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / doctrine / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / natalRebirthSignatures / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {
-            "contact": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "meaning": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "orb": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "contact": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "meaning": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "orb": {
+              "type": [
+                "number",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / rebirthThemes / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {
-            "frequencies": {
-              "anyOf": [
-                {
-                  "items": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  },
-                  "type": "array"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "period": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "rebirthTheme": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "transitPlanet": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "frequencies": {
+              "anyOf": [
+                {
+                  "items": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "type": "array"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "period": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "rebirthTheme": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "transitPlanet": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / source / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / source / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedOct 5, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new operational context: the POST endpoint and the 10-credit Tier 1 cost, which matters for an agent budgeting calls. It does not add anything about computation semantics (which zodiac or house defaults are applied), but the output schema covers the return side.

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?

One-sentence purpose followed by scannable bracketed metadata lines; nothing is padded and the required inputs and cost are front-loaded. The only redundancy is the alias line, which is short enough to earn its place by disambiguating near-duplicate tool names.

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

Completeness2/5

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

For a 15-parameter chart-computation tool this is thin: it says what inputs are mandatory but not what the computation does, which defaults apply, or how the 'rebirth' framing is produced. The existence of an output schema excuses it from describing return values, but the interpretive/behavioral gaps remain for a costly, complex call.

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?

The description only restates the four required parameters already enforced by the schema, adding no meaning. With 15 parameters and 33% schema description coverage, several inputs (city, name, cosmogram, ayanamsaId, zodiacType, houseSystem enum codes) are undocumented in both places, and the description does nothing to compensate — notably it never states the tropical/sidereal or house-system defaults that would change the result.

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

Purpose3/5

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

"Reframe major transits as rebirth" gives a verb and an object, and the alias line ties it to the canonical `astroway_psychological_modern_rudhyar_transits_as_rebirth`, so the agent knows which lineage (Rudhyar, modern psychological) it is in. But the phrasing is metaphorical: it never says whether the output is an interpretation text, a transit list, or a phase analysis, so the agent cannot distinguish its result from siblings like `astroway_psyr_cycles_of_becoming` or `astroway_psyr_lunation_phase`.

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 sibling is named as an alternative, despite several Rudhyar-family siblings in the list. The bracketed metadata (group, endpoint, required params, cost) tells the agent how to call it, not when to prefer it.

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

All AstroWay Psychological astrology 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?