AstroWay Astrology API (full catalogue)

Explain Transit

astroway_mcp_ai_explain_transit

Read-only

Explain a current transit hitting your natal chart.

[Group: AI & MCP] [Endpoint: POST /v1/ai/explain-transit] [Required: chart, transitDate, transitPlanet, natalPlanet, aspectType] [Cost: 100 credits (Tier 4)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chart": "<chart>",
      "transitDate": "<transitDate>",
      "transitPlanet": "<transitPlanet>",
      "natalPlanet": "<natalPlanet>",
      "aspectType": "<aspectType>"
    },
    "name": "astroway_mcp_ai_explain_transit"
  }
}

Input Schema

Name	Required	Description	Default
`chart`	Yes	Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as "Placidus" is refused, and the case matters because I and i are two different Sunshine systems.
`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.
`language`	No		uk
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`aspectType`	Yes
`natalPlanet`	Yes
`transitDate`	Yes
`transitPlanet`	Yes

Output Schema

Name	Required	Description	Default
`explanation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 7, 2026
- removedInput schema / properties / chart / properties / ayanamsaId / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / chart / properties / ayanamsaId / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / explanation / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / explanation / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / chart / description

Previous value: -"Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."New value: +"Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."

First observedOct 5, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-schema behavior: a 100-credit Tier 4 cost and the POST endpoint, which tells an agent this call is expensive and billable. It still says nothing about what the explanation contains or how long it runs, so it stops short of rich behavioral context.

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?

The purpose sentence is front-loaded and wastes no words, and the metadata block is scannable. The bracketed group/endpoint/cost lines are a slight structural tax but each carries real information an agent can use.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the nested chart object is documented thoroughly in the schema itself. Still, for an AI-interpretation tool with 8 parameters, a default language of 'uk', and a credit cost, the description feels thin: nothing explains the nature, length, or variability of the generated explanation, and no idempotency caveat beyond the annotation.

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?

Schema description coverage is only 38% across 8 parameters, so the description needed to compensate and does not. It merely repeats the five required names; it never says what values transitPlanet and natalPlanet accept ("Sun", "Moon"?) or how aspectType interacts with the supplied planets, leaving the low-coverage parameters undocumented in both places.

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?

"Explain a current transit hitting your natal chart" gives a specific verb (explain) plus the resource (a transit-to-natal aspect), which is enough to separate it from chart-calculation siblings like astroway_bazi_chart. It never names the closest sibling, astroway_mcp_ai_explain_aspect, and "current" sits oddly against a transitDate parameter that accepts any date.

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 guidance, no prerequisites, and no exclusions or alternatives. The only routing help is a bare required-parameter list, which restates the schema rather than telling an agent when to pick this over astroway_mcp_ai_explain_aspect.

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?