astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Parent-Child Deep

astroway_family_parent_child_deep

Read-onlyIdempotent

Analyze deep parent-child synastry from both birth charts to reveal inherited patterns and relationship dynamics between a parent and child.

Instructions

Deep parent-child synastry analysis.

[Group: Family Astrology] [Endpoint: POST /v1/family/parent-child-deep] [Required: parent, child] [Cost: 10 credits (Tier 1)]

Input Schema

Name	Required	Description	Default
`child`	Yes	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.
`parent`	Yes	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.

Output Schema

Name	Required	Description	Default
`source`	No
`mcContact`	No
`disclaimer`	No
`interpretation`	No
`luminaryAspects`	No
`inheritanceScore`	No
`saturnCrossCount`	No
`parentalAxisOverlay`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.0Oct 24, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful operational context -- the HTTP endpoint and the 10-credit Tier 1 cost -- but says nothing about what the 'deep' analysis returns or how large it is.

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 functional sentence is front-loaded and the metadata block is compact. The '[Required: parent, child]' line duplicates the schema's required array, which is the only wasted element.

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 and fully documented parameters, the definition is callable as-is. What remains missing is a sense of what the deep analysis produces and how it differs from the shallower family/synastry tools, which matters given ~700 siblings.

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 objects are documented in exhaustive detail, so the schema carries the burden. The description only restates that parent and child are required, adding no meaning beyond the schema.

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 deep synastry analysis between a parent and a child. The 'parent-child' qualifier does distinguish it from relational/group synastry tools, but it never names a nearby sibling (e.g. astroway_family_sibling_dynamics or astroway_ai_interpret_synastry) to clarify boundaries.

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?

Beyond listing the two required inputs, there is no guidance on when to choose this over family_genogram, sibling_dynamics, or the generic synastry endpoints. No prerequisites or exclusions are given; the agent must infer usage from the name alone.

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

Deploy Server