astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Essential Dignities

astroway_dignities_essential_dignities

Read-onlyIdempotent

Calculate the five Ptolemaic essential dignities and debilities for each planet from birth data to assess planetary strength in a natal chart.

Instructions

Calculate the five Ptolemaic essential dignities (rulership, exaltation, triplicity, term, face) and debilities for each planet.

[Group: Dignities & Receptions] [Endpoint: POST /v1/essential-dignities] [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_essential_dignities"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Natal chart plus optional custom terms and decans tables.

Output Schema

Name	Required	Description	Default
`dignities`	No
`totalScore`	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

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely operational context beyond that: the endpoint (POST /v1/essential-dignities) and a per-call cost of 20 credits at Tier 2, which lets an agent budget calls. It does not describe error or validation behavior, but that is largely carried by the schema.

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 core sentence is front-loaded, single-sentence and waste-free, with the five dignity types enumerated rather than implied. The trailing bracket block (group, endpoint, cost) is structured metadata rather than prose, so it is cheap to scan.

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 return values need not be explained, and the deeply described input schema covers birth data and optional custom tables. What remains thin is guidance on defaults that materially change results (tropical vs sidereal, houseSystem) and why one would request custom terms; those are discoverable in the schema rather than the description.

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%, and the nested birth-data schema documents every field (date/time patterns, timezone vs timezoneOffset precedence, houseSystem letter codes, custom termsData/decansData). The description adds no parameter-level meaning at all, which is the correct baseline of 3 when the schema does the work.

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?

Names a specific verb (Calculate) and resource (essential dignities), and enumerates the five Ptolemaic components plus debilities, so the agent knows the exact technique. It is distinguishable from siblings like almuten or receptions by content, though it never explicitly contrasts itself with them.

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 or when-not-to-use guidance and no named alternative among the dignity siblings (almuten, receptions, disposition_chains). The phrase 'for each planet' implies scope, but the agent must infer the use case entirely from the tool name.

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

Deploy Server