AstroWay Human Design

Chart-grounded AI chat

astroway_mcp_ai_chat

Read-only

Chat answered from the positions we computed for this birth moment, not from the model's memory of a sun sign. Carries up to 10 turns of history, replies in 21 languages, and takes four voices through persona. Send your own provider key and the turn costs 5 credits instead of the endpoint price.

[Group: AI & MCP] [Endpoint: POST /v1/ai/chat] [Required: message] [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": {
      "message": "<message>"
    },
    "name": "astroway_mcp_ai_chat"
  }
}

Input Schema

Name	Required	Description	Default
`chart`	No	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.
`history`	No
`message`	Yes
`persona`	No		astrologer
`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.

Output Schema

Name	Required	Description	Default
`model`	No
`reply`	No
`tokens`	No
`persona`	No
`language`	No
`disclaimer`	No
`duration_ms`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 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 / disclaimer / anyOf

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

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

removedOutput schema / properties / duration_ms / anyOf

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

addedOutput schema / properties / duration_ms / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / language / anyOf

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

addedOutput schema / properties / language / 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 / persona / anyOf

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

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

removedOutput schema / properties / reply / anyOf

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

addedOutput schema / properties / reply / 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"
+  }
+]

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

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, open-world, non-idempotent), and the description adds real context beyond them: a 10-turn history cap, 21 supported languages, the four persona voices, and a concrete cost differential (5 credits with your own provider key vs the endpoint price). The main gap is that it implies chart grounding is essential while the schema marks only `message` required, leaving unclear what happens when `chart` is omitted.

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?

Three short sentences, front-loaded with the differentiating claim, followed by compact machine-readable metadata for endpoint, required field, and cost. The rhetorical contrast with 'the model's memory of a sun sign' is slightly promotional but earns its place by conveying the grounding behavior.

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 and the nested chart object is documented inside the schema, so the description need not restate return values or birth-data rules. What is left loose is the chart-optional-versus-chart-required question and the relationship between the stated 5-credit key path and the Tier-4 100-credit list price.

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?

At 43% schema description coverage the description must carry weight, and it does explain three parameters in passing: `persona` (four voices), `history` (up to 10 turns), and `language` (21 languages). It says nothing about `chart`, `fields`, or `precision`, though the nested chart object is itself richly documented in the schema, so the net gap is moderate.

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 states a specific verb and resource: a chat whose answers are derived from computed natal-chart positions rather than from the model's generic sun-sign memory. That grounding clause distinguishes it in spirit from siblings like ai_explain_aspect or ai_explain_transit, but no sibling is named or compared, so the differentiation is implicit rather than explicit.

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?

It describes what the tool is and what it carries (history, languages, personas, cost), but never says when to pick it over ai_comparison_coach, ai_explain_transit, or rag_search, and gives no when-not guidance or prerequisites. Usage is only inferable from the chart-grounding framing.

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

All AstroWay Human Design 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?