Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Sibling Dynamics

astroway_family_sibling_dynamics
Read-onlyIdempotent

Compare two siblings' birth charts to analyze their relationship dynamics, synastry, and inter-sibling compatibility patterns.

Instructions

Inter-sibling synastry and dynamics.

[Group: Family Astrology] [Endpoint: POST /v1/family/sibling-dynamics] [Required: sibling1, sibling2] [Cost: 10 credits (Tier 1)]

Input Schema

NameRequiredDescriptionDefault
parentNoBirth 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.
sibling1YesBirth 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.
sibling2YesBirth 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

NameRequiredDescriptionDefault
sourceNo
disclaimerNo
moonAspectNo
siblingScoreNo
mercuryAspectNo
interpretationNo
sharedParentImprintNo
siblingHouseOverlayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds genuinely new operational facts — the POST endpoint and a 10-credit Tier 1 cost — which is real value beyond the annotations, but it says nothing about what the analysis returns or why an optional parent chart would be supplied.

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 content sentence followed by a compact bracketed metadata block, front-loaded with no filler. The bracketed lines are machine-style repetitions of schema facts, but they are short and the endpoint/cost line earns its place.

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 and the input schema is exhaustively documented, so the description needn't carry the return format or coordinate rules. What remains missing is scope framing (why the optional parent chart matters) and any sense of what 'dynamics' means in the response.

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 heavily documented in-schema, so parameter semantics are largely handled there; baseline 3 applies. The description does not mention the optional 'parent' parameter at all, missing the one chance to explain a non-obvious input.

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 phrase 'Inter-sibling synastry and dynamics' names the resource (two siblings' charts compared) and implies a comparison output, but there is no verb and 'dynamics' is amorphous about what is actually computed. It does implicitly separate itself from astroway_relational_synastry and astroway_family_parent_child_deep by scope, but never states that distinction explicitly.

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?

No when-to-use guidance and no alternatives are named, even though the sibling set includes astroway_family_parent_child_deep, astroway_family_genogram, astroway_family_system_pattern and astroway_relational_synastry. The '[Required: sibling1, sibling2]' line only restates the schema's required array rather than helping the agent choose this tool.

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

Deploy Server

Other Tools