astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Family System Pattern

astroway_family_system_pattern

Read-onlyIdempotent

Analyze family astrological signatures from two to eight members' birth data to identify system-level patterns and relationship dynamics.

Instructions

System-level family astrological signatures.

[Group: Family Astrology] [Endpoint: POST /v1/family/system-pattern] [Required: members] [Cost: 10 credits (Tier 1)]

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": {
      "members": "<members>"
    },
    "name": "astroway_family_system_pattern"
  }
}

Input Schema

Name	Required	Description	Default
`members`	Yes

Output Schema

Name	Required	Description	Default
`source`	No
`members`	No
`disclaimer`	No
`systemSummary`	No
`excludedThemes`	No
`generationalShadow`	No
`luminaryGhostContacts`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.6.1Nov 9, 2026

changedInput schema / properties / members / items / 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": {
-      "role": {
-        "enum": [
-          "parent",
-          "child",
-          "grandparent",
-          "sibling",
-          "spouse"
-        ],
-        "type": "string"
-      }
-    },
-    "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": {
+      "role": {
+        "enum": [
+          "parent",
+          "child",
+          "grandparent",
+          "sibling",
+          "spouse"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]

changedInput schema / properties / members / 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."

Addedv1.6.0Oct 24, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is covered. The description adds the 10-credit cost and endpoint, which is useful operational context. The POST endpoint does not contradict readOnlyHint because it can be a read-only computation.

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 description is very short and front-loads the purpose before bracketed metadata. The metadata is compact and scannable, though group and endpoint details are less essential. There is no bloated prose.

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

Completeness2/5

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

For a complex family-system computation over 2-8 member birth records, the description omits what the resulting signature means and when to use it. An output schema exists, so return values need not be described, but the input and usage context remain thin. It is incomplete relative to the tool's complexity.

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?

The top-level "members" parameter has 0% schema description coverage, and the description only repeats "Required: members." It does not explain the 2-8 array bounds, member birth-data fields, or role values, so it fails to compensate for the top-level schema gap. Nested schema descriptions cover birth data, but the description adds no meaning beyond the required marker.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a vague noun phrase, "System-level family astrological signatures," which identifies the family-astrology domain but no specific operation. It does not differentiate this tool from sibling family tools such as genogram or parent-child deep.

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, no prerequisites, and no alternative named. The bracket metadata lists group, endpoint, required parameter, and cost, but not selection criteria.

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

Deploy Server