Skip to main content
Glama

Western Astrology MCP Server by RoxyAPI

Monthly Parallels - Declination contacts for an entire month

post_astrology_parallels_monthly
Read-only

Get every parallel and contraparallel of declination that perfects during a given month, across the 13 non-lunar Western bodies: the Sun and Mercury through Pluto, both lunar nodes, Chiron and Black Moon Lilith. A parallel is two bodies at the same declination and reads much like a conjunction; a contraparallel is equal and opposite declinations and reads much like an opposition. Neither depends on zodiacal distance, so they surface connections an aspect table cannot show, which is why traditional and modern practitioners read them alongside aspects. Declinations are geocentric, matching what an ephemeris publishes. Returns the exact date and time of closest approach in your timezone with both declinations. The Moon is excluded because its declination swings the full range every month and would bury the slow pairs. Omit year and month to get the month in progress, so a published calendar stays current without a redeploy. Essential for declination work, out-of-bounds tracking, monthly forecast copy, and electional timing. Monthly parallel calendar API, declination aspects, contraparallel ephemeris. Verified against NASA JPL Horizons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orbNoHow far from exact still counts, in degrees. The traditional orb for a declination contact is tighter than for a zodiacal aspect because declination changes slowly. Defaults to 1.5.
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
yearNoYear for the declination calendar (1551 to 2649). Defaults to the current year (UTC).
monthNoMonth number (1-12). Defaults to the current month (UTC).
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.
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
timezoneNoTimezone: 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 once, at the start of the window, and that offset applies to every time in the response. Event dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
orbYes
yearYes
monthYes
eventsYes
timezoneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / timezone / example
      Previous value: --5New value: +"America/New_York"
  2. Changed3 schema fields changed
    • changedInput schema / properties / year / description
      Previous value: -"Year for the declination calendar (1900-2100). Defaults to the current year (UTC)."New value: +"Year for the declination calendar (1551 to 2649). Defaults to the current year (UTC)."
    • changedInput schema / properties / year / maximum
      Previous value: -2100New value: +2649
    • changedInput schema / properties / year / minimum
      Previous value: -1900New value: +1551
  3. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone offset from UTC in hours. Event dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC)."New value: +"Timezone: 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 once, at the start of the window, and that offset applies to every time in the response. Event dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC)."
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "events": {
      +      "items": {
      +        "properties": {
      +          "date": {
      +            "type": "string"
      +          },
      +          "datetime": {
      +            "type": "string"
      +          },
      +          "declination1": {
      +            "type": "number"
      +          },
      +          "declination2": {
      +            "type": "number"
      +          },
      +          "orb": {
      +            "type": "number"
      +          },
      +          "planet1": {
      +            "type": "string"
      +          },
      +          "planet1Localized": {
      +            "type": "string"
      +          },
      +          "planet2": {
      +            "type": "string"
      +          },
      +          "planet2Localized": {
      +            "type": "string"
      +          },
      +          "time": {
      +            "type": "string"
      +          },
      +          "type": {
      +            "enum": [
      +              "parallel",
      +              "contraparallel"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "planet1",
      +          "planet2",
      +          "type",
      +          "date",
      +          "time",
      +          "datetime",
      +          "orb",
      +          "declination1",
      +          "declination2"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "month": {
      +      "type": "number"
      +    },
      +    "orb": {
      +      "type": "number"
      +    },
      +    "timezone": {
      +      "type": "number"
      +    },
      +    "year": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "year",
      +    "month",
      +    "timezone",
      +    "orb",
      +    "events"
      +  ],
      +  "type": "object"
      +}
  5. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"Response 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."
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "tr",
      -  "de",
      -  "es",
      -  "hi",
      -  "pt",
      -  "fr",
      -  "ru"
      -]New value: +[
      +  "en",
      +  "tr",
      +  "de",
      +  "es",
      +  "hi",
      +  "pt",
      +  "fr",
      +  "ru",
      +  "zh-Hans",
      +  "zh-Hant"
      +]
  6. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description still adds real value beyond that: the geocentric frame matching ephemerides, the deliberate exclusion of the Moon and its rationale, and the fact that returned times are localized to the caller's timezone with exact closest-approach instants.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core content is front-loaded and each explanatory sentence (Moon exclusion, geocentric frame, return contents) earns its place. However, the trailing SEO keyword string ('Monthly parallel calendar API, declination aspects, contraparallel ephemeris. Verified against NASA JPL Horizons.') is filler that dilutes an otherwise tight definition.

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

Completeness5/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 all seven parameters fully described, the description needn't explain return shapes, and it still covers the interpretive context (parallel≈conjunction, contraparallel≈opposition), the excluded body, and the reference frame. Nothing an agent needs to call this correctly is missing.

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 schema already documents orb, lang, year, month, compact, nodeType, and timezone in detail, so the baseline is 3. The description adds little parameter-specific syntax beyond reinforcing that year/month are optional and timezone drives reported event times.

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 ('Get every parallel and contraparallel of declination'), a precise resource (declination contacts for a month), and enumerates the exact body set (13 non-lunar Western bodies, Moon excluded). This cleanly separates it from the aspect-oriented siblings like post_astrology_aspects_monthly, since it explicitly notes these contacts are not zodiacal-distance based.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage contexts ('declination work, out-of-bounds tracking, monthly forecast copy, electional timing') and explains when defaults apply ('Omit year and month to get the month in progress'). It also implies contrast with aspect tables ('surface connections an aspect table cannot show') but never names a specific sibling tool to use instead, so routing is inferred rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources