Skip to main content
Glama
RoxyAPI

RoxyAPI Astrology MCP server

Official
by RoxyAPI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Detect aspect patterns - Grand Trine, Kite, T-Square, Grand Cross, Yod, Mystic Rectangle, Stellium

post_astrology_aspect_patterns
Read-only

Detect Grand Trines, T-Squares, Yods, and other multi-planet patterns in a birth chart, with tightness scores, disambiguation, and one-line interpretations.

Instructions

Identify classical Western astrology multi-planet configurations in a birth chart. Returns Grand Trines (with element), Kites (with apex), T-Squares (with apex and modality), Grand Crosses (with modality), Yods (Finger of Fate, with apex), Mystic Rectangles, and Stelliums. Each pattern carries a tightness score (0-100), dissociate flag for out-of-sign configurations, and a one-line interpretation suitable for chart reports. Disambiguation is built in: a Grand Cross suppresses its contained T-Squares, a Kite suppresses its underlying Grand Trine. Useful for personalized natal report engines, astrology chatbots, AI agents that interpret chart geometry, and editorial chart-pattern callouts.

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
langNoResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.en
timeYesBirth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
compactNoSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
includeNoComma-separated list of optional bodies to include beyond the classical 10 planets. Valid tokens (case-insensitive): chiron, northNode (also accepts north_node, north-node, northnode). Empty by default.
latitudeYesBirth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
nodeTypeNoLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass "mean" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to "true".true
timezoneYesTimezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.
longitudeYesBirth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.
strictOrbsNoUse tighter orbs, so only closely formed patterns are reported. Truthy values (true, 1, yes, on; case-insensitive) narrow trine to 5 degrees, square to 5, sextile to 4, quincunx to 2. Defaults to false, the standard pattern-detection orbs.

Output Schema

NameRequiredDescriptionDefault
totalYes
optionsYes
patternsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.2
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "1990-07-15",
-    "latitude": 40.7128,
-    "longitude": -74.006,
-    "time": "14:30:00",
-    "timezone": -5
-  }
-]New value: +[
+  {
+    "date": "1990-07-15",
+    "latitude": 40.7128,
+    "longitude": -74.006,
+    "time": "14:30:00",
+    "timezone": "America/New_York"
+  }
+]
    • changedInput schema / properties / timezone / example
      Previous value: --5New value: +"America/New_York"
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only cover safety (readOnly, non-destructive); the description adds genuinely useful behavioral detail beyond that: what each pattern object carries (tightness score 0-100, dissociate flag, one-line interpretation) and the built-in suppression rule where a Grand Cross suppresses contained T-Squares and a Kite suppresses its underlying Grand Trine. It doesn't discuss orbs/tolerance behavior or failure modes, but the disclosure is well above the annotation baseline.

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?

Front-loaded with the core purpose, followed by return contents and the suppression rule, all of which earn their place. The trailing audience list ('useful for ... and editorial chart-pattern callouts') is the one soft sentence, but the rest is dense and well-ordered.

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?

With an output schema present, the description need not explain return values, yet it usefully summarizes them; 5 required and 10 total parameters are fully documented in the schema, and the pattern vocabulary is complete. The only real gap is sibling-level routing guidance, which the description leaves implicit.

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 parameters (including strictOrbs orb-narrowing behavior, include tokens, nodeType, compact) are already fully documented in the schema. The description mentions no parameter at all, adding no semantic value beyond what structured fields provide; baseline 3 applies.

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

Purpose5/5

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

States a specific verb (identify/detect) and resource (classical Western multi-planet configurations in a birth chart), then enumerates the exact pattern types returned (Grand Trine, Kite, T-Square, Grand Cross, Yod, Mystic Rectangle, Stellium). This clearly separates it from the pairwise-modifier sibling post_astrology_aspects without the agent needing to open either schema.

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?

The closing sentence lists audiences ('personalized natal report engines, astrology chatbots, AI agents that interpret chart geometry'), which implies usage context but is audience-oriented rather than decision-oriented. It never states when to prefer this over post_astrology_aspects, post_astrology_natal_chart, or post_astrology_transit_aspects, nor any prerequisites. Usage is inferable from the pattern list but not explicitly guided.

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