astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Hyleg & Alcocoden

astroway_dignities_hyleg

Read-onlyIdempotent

Calculates the Hyleg (apheta) and Alcocoden from a natal chart using the traditional Hellenistic method to determine the giver of life and lifespan indicator.

Instructions

Calculate the Hyleg (apheta, giver of life) and Alcocoden (indicator of lifespan) using traditional Hellenistic method.

[Group: Dignities & Receptions] [Endpoint: POST /v1/hyleg] [Cost: 20 credits (Tier 2)]

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": {
      "body": "<body>"
    },
    "name": "astroway_dignities_hyleg"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Natal chart plus the hyleg method and optional custom dignity tables.

Output Schema

Name	Required	Description	Default
`hyleg`	No
`alcocoden`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.1Nov 9, 2026

changedInput schema / properties / body / allOf

Previous value: -[
-  {
-    "additionalProperties": {
-      "anyOf": [
-        {},
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "description": "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.",
-    "properties": {
-      "ayanamsa": {
-        "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
-        "enum": [
-          "fagan-bradley",
-          "lahiri",
-          "de-luce",
-          "raman",
-          "krishnamurti",
-          "kp",
-          "yukteshwar",
-          "jn-bhasin",
-          "true-citra",
-          "djwhal-khul"
-        ],
-        "type": "string"
-      },
-      "ayanamsaId": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "city": {
-        "default": "",
-        "type": "string"
-      },
-      "cosmogram": {
-        "type": "boolean"
-      },
-      "date": {
-        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-        "type": "string"
-      },
-      "houseSystem": {
-        "default": "P",
-        "enum": [
-          "P",
-          "K",
-          "R",
-          "C",
-          "E",
-          "W",
-          "B",
-          "M",
-          "O",
-          "A",
-          "T",
-          "V",
-          "D",
-          "F",
-          "G",
-          "H",
-          "I",
-          "i",
-          "L",
-          "N",
-          "Q",
-          "S",
-          "U",
-          "X",
-          "Y"
-        ],
-        "type": "string"
-      },
-      "latitude": {
-        "maximum": 90,
-        "minimum": -90,
-        "type": "number"
-      },
-      "longitude": {
-        "maximum": 180,
-        "minimum": -180,
-        "type": "number"
-      },
-      "name": {
-        "default": "",
-        "type": "string"
-      },
-      "time": {
-        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
-        "type": "string"
-      },
-      "timezone": {
-        "description": "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.",
-        "type": "string"
-      },
-      "timezoneOffset": {
-        "anyOf": [
-          {
-            "maximum": 14,
-            "minimum": -14,
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": 0,
-        "description": "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."
-      },
-      "zodiacType": {
-        "enum": [
-          "tropical",
-          "sidereal"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "date",
-      "time",
-      "latitude",
-      "longitude"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": {
-      "anyOf": [
-        {},
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "properties": {
-      "decansData": {
-        "items": {
-          "properties": {
-            "decans": {
-              "items": {
-                "type": "string"
-              },
-              "type": "array"
-            },
-            "sign": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "sign",
-            "decans"
-          ],
-          "type": "object"
-        },
-        "maxItems": 12,
-        "type": "array"
-      },
-      "termsData": {
-        "items": {
-          "anyOf": [
-            {
-              "properties": {
-                "sign": {
-                  "type": "string"
-                },
-                "terms": {
-                  "items": {
-                    "properties": {
-                      "endDegree": {
-                        "type": "number"
-                      },
-                      "planet": {
-                        "type": "string"
-                      }
-                    },
-                    "required": [
-                      "endDegree",
-                      "planet"
-                    ],
-                    "type": "object"
-                  },
-                  "maxItems": 12,
-                  "type": "array"
-                }
-              },
-              "required": [
-                "sign",
-                "terms"
-              ],
-              "type": "object"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "maxItems": 12,
-        "type": "array"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "description": "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.",
+    "properties": {
+      "ayanamsa": {
+        "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
+        "enum": [
+          "fagan-bradley",
+          "lahiri",
+          "de-luce",
+          "raman",
+          "krishnamurti",
+          "kp",
+          "yukteshwar",
+          "jn-bhasin",
+          "true-citra",
+          "djwhal-khul"
+        ],
+        "type": "string"
+      },
+      "ayanamsaId": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "city": {
+        "default": "",
+        "type": "string"
+      },
+      "cosmogram": {
+        "type": "boolean"
+      },
+      "date": {
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "houseSystem": {
+        "default": "P",
+        "enum": [
+          "P",
+          "K",
+          "R",
+          "C",
+          "E",
+          "W",
+          "B",
+          "M",
+          "O",
+          "A",
+          "T",
+          "V",
+          "D",
+          "F",
+          "G",
+          "H",
+          "I",
+          "i",
+          "L",
+          "N",
+          "Q",
+          "S",
+          "U",
+          "X",
+          "Y"
+        ],
+        "type": "string"
+      },
+      "latitude": {
+        "maximum": 90,
+        "minimum": -90,
+        "type": "number"
+      },
+      "longitude": {
+        "maximum": 180,
+        "minimum": -180,
+        "type": "number"
+      },
+      "name": {
+        "default": "",
+        "type": "string"
+      },
+      "time": {
+        "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
+        "type": "string"
+      },
+      "timezone": {
+        "description": "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.",
+        "type": "string"
+      },
+      "timezoneOffset": {
+        "anyOf": [
+          {
+            "maximum": 14,
+            "minimum": -14,
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": 0,
+        "description": "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."
+      },
+      "zodiacType": {
+        "enum": [
+          "tropical",
+          "sidereal"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "date",
+      "time",
+      "latitude",
+      "longitude"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "properties": {
+      "decansData": {
+        "items": {
+          "properties": {
+            "decans": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "sign": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "sign",
+            "decans"
+          ],
+          "type": "object"
+        },
+        "maxItems": 12,
+        "type": "array"
+      },
+      "termsData": {
+        "items": {
+          "anyOf": [
+            {
+              "properties": {
+                "sign": {
+                  "type": "string"
+                },
+                "terms": {
+                  "items": {
+                    "properties": {
+                      "endDegree": {
+                        "type": "number"
+                      },
+                      "planet": {
+                        "type": "string"
+                      }
+                    },
+                    "required": [
+                      "endDegree",
+                      "planet"
+                    ],
+                    "type": "object"
+                  },
+                  "maxItems": 12,
+                  "type": "array"
+                }
+              },
+              "required": [
+                "sign",
+                "terms"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "maxItems": 12,
+        "type": "array"
+      }
+    },
+    "type": "object"
+  }
+]

Addedv1.6.0Oct 24, 2026

TDQS

A3.5/5.0

Behavior3/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 bar is lower. The description still adds genuinely useful operational context that annotations cannot convey: the POST /v1/hyleg endpoint and a 20-credit Tier 2 cost. It says nothing about what the calculation returns or what happens when the required birth data is malformed, though the output schema partly relieves the former.

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 front-loaded sentence states the purpose, followed by three short bracketed metadata lines (group, endpoint, cost) that each carry real information. No filler, though the bracketed lines are somewhat boilerplate and the cost line is the only one that materially affects an agent's decision.

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?

For a calculation tool with a fully documented schema and an output schema, the definition covers what it does, which school it implements, and what it costs. What is missing is routing guidance against the sibling longevity tool and any hint about the result's components, but nothing essential for a correct invocation is absent.

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 description coverage is 100%, so the schema fully documents the single nested body parameter, including the birth-data contract and the optional termsData/decansData tables. The description adds no meaning beyond that — nothing about how the custom dignity tables alter the Hyleg/Alcocoden determination. Baseline 3 is correct when the schema carries the load.

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 gives a specific verb ('Calculate') and names both resources, Hyleg (apheta, giver of life) and Alcocoden (indicator of lifespan), with glosses that make the jargon legible. It also pins the method to the 'traditional Hellenistic' school. It does not differentiate from the sibling astroway_hellenistic_hand_longevity_hyleg, which sounds like an adjacent longevity calculation, so it falls short of a 5.

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 through the method scope ('traditional Hellenistic method') and the group tag 'Dignities & Receptions'. There is no explicit statement of when to choose this over the Hyleg/longevity sibling, no prerequisites such as needing a full natal chart, and no note on how custom terms/decan tables change the result.

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

Deploy Server