AstroWay Astrology API (full catalogue)

AI Transit Narrative (single date)

astroway_reports_ai_transit_narrative

Snapshot transit interpretation for a specific date. Inputs: chart + transitDate (+optional transitTime/tzOffset), language, tone, length. Returns narrative grounded in transit-to-natal aspects (orb ≤1°).

[Group: AI Reports] [Endpoint: POST /v1/reports/ai/transit-narrative] [Cost: 250 credits (Tier 5)] ⚠️ Heavy — confirm with user before invoking.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_reports_ai_transit_narrative"
  }
}

Input Schema

Name	Required	Description
`date`	No
`time`	No
`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. Krishnamurti ("kp") when omitted on KP routes. Equivalent to ayanamsaId; send either.
`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.
`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	Sidereal mode, the standard numeric ayanamsa ids. 5 (Krishnamurti) when omitted on KP routes; 1 is Lahiri.
`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
`model`	No
`tokens`	No
`narrative`	No
`disclaimer`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 15, 2026

changedInput schema / properties / ayanamsaId / description

Previous value: -"Swiss Ephemeris sidereal mode. 5 (Krishnamurti) when omitted on KP routes; 1 is Lahiri."New value: +"Sidereal mode, the standard numeric ayanamsa ids. 5 (Krishnamurti) when omitted on KP routes; 1 is Lahiri."

Changed2 schema fields changedNov 14, 2026

changedInput schema / properties / ayanamsa / description

Previous value: -"Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either."New value: +"Sidereal school by name. Krishnamurti (\"kp\") when omitted on KP routes. Equivalent to ayanamsaId; send either."

addedInput schema / properties / ayanamsaId / description

Added value: +"Swiss Ephemeris sidereal mode. 5 (Krishnamurti) when omitted on KP routes; 1 is Lahiri."

Changed9 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 / model / anyOf

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

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

removedOutput schema / properties / narrative / anyOf

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

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

changedOutput schema / properties / tokens / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "input": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "output": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "input": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "output": {
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations (which only say readOnly=false, non-idempotent, open-world), the description discloses the billing cost and tier, warns that the call is heavy and requires user confirmation, and states the output is grounded in transit-to-natal aspects with orb ≤1°. That is substantive behavioral context an agent cannot get from the structured fields; it does not state latency or failure modes.

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?

Two front-loaded sentences plus three bracketed metadata lines; the cost warning is placed last where it is most visible and every element carries information. The inline input enumeration is the one partly redundant piece, since the schema already lists the parameters.

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?

An output schema exists, so the description need not explain return shape, and it still gives a one-line summary of what the narrative is grounded in. Cost, confirmation requirement, endpoint and grouping are all present; the only gap is the absence of any routing versus the several transit-related siblings.

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 coverage is 75%, so the baseline is 3, and the description roughly maps optionality ("chart + transitDate (+optional transitTime/tzOffset)"). However it also advertises inputs named "language, tone, length" that do not appear anywhere in the supplied schema, which is a real mismatch rather than added meaning.

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?

"Snapshot transit interpretation for a specific date" gives a concrete verb and resource, and the scope word "snapshot" plus the title's "single date" makes clear this is a one-date transit read rather than a period report. It never names the near neighbours (astroway_ai_explain_transit, astroway_ai_interpret_transits, astroway_reports_transit_yearly), so sibling disambiguation is left to the agent.

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

Usage Guidelines3/5

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

The one explicit directive is the cost gate: "250 credits (Tier 5) ⚠️ Heavy — confirm with user before invoking," which is genuinely actionable usage guidance. There is no statement of when to choose this over the transit-explanation or yearly-transit siblings, so the when/when-not dimension is only implied.

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

All AstroWay Astrology API (full catalogue) 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?