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 (1900-2100). 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 / 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)."
  2. 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"
      +}
  3. 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"
      +]
  4. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial non-obvious behavior: the Moon is deliberately excluded, declinations are geocentric, exact date/time of closest approach is returned in the requested timezone, and omitting year/month returns the current month so calendars stay current. There is no contradiction between the description and the annotations.

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 key scope is front-loaded and the first sentence is excellent, but the description is long and includes astrological background and a closing keyword string ('Monthly parallel calendar API, declination aspects, contraparallel ephemeris') that add little for an agent selecting or invoking the tool. Most sentences earn their place, but a few could be trimmed.

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?

For a 7-parameter tool with no required parameters and an output schema, the description covers the body set, the meaning of parallels and contraparallels, timezone behavior, the current-month shortcut, and why the Moon is excluded. The output schema handles return-shape details, so nothing critical is missing for correct selection and invocation.

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?

Input schema coverage is 100%, so parameters like orb, lang, year, month, compact, nodeType, and timezone are already well documented. The description adds only small contextual notes, such as timezone-aware return times and the omit-year/month behavior, which is appropriate but does not need to restate the schema.

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?

The description opens with a specific verb and resource: 'Get every parallel and contraparallel of declination that perfects during a given month,' and enumerates exactly which 13 bodies are included. It also distinguishes the tool from sibling aspect tools by explaining that declination contacts are independent of zodiacal distance and surface connections aspect tables cannot show.

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?

The description gives concrete use cases ('declination work, out-of-bounds tracking, monthly forecast copy, and electional timing') and positions the tool relative to aspect reading ('read them alongside aspects'). It does not explicitly name an alternative sibling or state when not to use this tool, so it stops short of full routing guidance.

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