AstroWay Astrology API (full catalogue)

Penta Chart

astroway_hd_penta

Read-onlyIdempotent

Calculate the Penta (group) chart for 3–5 people: combined BodyGraph showing group dynamics and collective conditioning.

[Group: Human Design] [Endpoint: POST /v1/hd/penta] [Required: inputs] [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": {
      "inputs": "<inputs>"
    },
    "name": "astroway_hd_penta"
  }
}

Input Schema

Name	Required	Description
`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.
`inputs`	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.

Output Schema

Name	Required	Description	Default
`role`	No
`size`	No
`channels`	No
`definedCenters`	No
`pentaAuthority`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 7, 2026

removedInput schema / properties / inputs / items / properties / ayanamsaId / anyOf

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

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

changedOutput schema / properties / channels / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {
-            "defined": {
-              "anyOf": [
-                {
-                  "type": "boolean"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "id": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "defined": {
+              "type": [
+                "boolean",
+                "null"
+              ]
+            },
+            "id": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / definedCenters / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / pentaAuthority / anyOf

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

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

removedOutput schema / properties / role / anyOf

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

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

removedOutput schema / properties / size / anyOf

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

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

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / inputs / items / 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 (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the operational disclosure: a 100-credit Tier 4 cost and the POST /v1/hd/penta endpoint. Cost and tier are genuinely useful pre-call information not available in the annotations or schema, though nothing is said about latency, failure modes, or what a partial/degenerate input set produces.

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 substantive sentence is front-loaded and free of filler, followed by a consistent bracketed metadata block (group, endpoint, required, cost). The block format is formulaic but each line carries distinct operational information, so nothing meaningful is wasted.

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?

With an output schema present, the description need not explain return values, and cost plus endpoint are disclosed. What is missing for a computational, credit-charged tool is disambiguation from the sibling group/relationship tools and any note on what happens when the supplied people number outside 3–5 or inputs are malformed.

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 67% and the nested birth-data object is heavily documented in the schema itself (timezone, timezoneOffset, houseSystem, city semantics). The description adds only the cardinality constraint (3–5 people) and the required 'inputs' parameter, so it neither compensates for the undocumented remainder nor adds syntax detail beyond the schema. Baseline 3 applies.

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 names a specific verb and resource ('Calculate the Penta (group) chart') and pins the scope to 3–5 people producing a 'combined BodyGraph showing group dynamics and collective conditioning'. That is concrete enough for an agent to know what it returns, but it never distinguishes the Penta from near-siblings such as astroway_hd_group_overlay or astroway_hd_human_design_compatibility, so the agent must infer the difference.

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?

Usage is only implied: the '3–5 people' phrasing signals the suitable group size, and the [Required: inputs] line signals that inputs must be sent. There is no explicit when-to-use vs when-not-to-use statement and no mention of the sibling tools that compute group overlays or compatibility, which is exactly the decision the agent faces.

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?