Western Astrology MCP Server by RoxyAPI

Get current moon phase - Lunar phase calculator with zodiac sign

get_astrology_moon_phase_current

Read-only

Get current moon phase with illumination percentage, lunar age (days since new moon), zodiac sign, and distance from Earth. Returns phase name (New Moon, Waxing Crescent Moon, First Quarter Moon, Waxing Gibbous Moon, Full Moon, Waning Gibbous Moon, Last Quarter Moon, Waning Crescent Moon) plus exact lunar position. Perfect for moon tracking apps, lunar calendars, astrology widgets, and gardening by moon phase tools.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Date in YYYY-MM-DD format. Defaults to today if omitted.
`lang`	No	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.	en
`time`	No	Time in 24-hour HH:MM:SS format. Defaults to 12:00:00 (noon). Moon moves ~13 degrees per day so time affects phase precision.
`compact`	No	Set 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.
`timezone`	No	IANA name (e.g. "America/New_York", "Europe/London"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00"). IANA resolved to the DST-correct offset for the given date. Defaults to 0 (UTC).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`age`	Yes
`date`	Yes
`sign`	Yes
`phase`	Yes
`degree`	Yes
`meaning`	No
`distance`	Yes
`illumination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "age": {
+      "type": "number"
+    },
+    "date": {
+      "type": "string"
+    },
+    "degree": {
+      "type": "number"
+    },
+    "distance": {
+      "type": "number"
+    },
+    "illumination": {
+      "type": "number"
+    },
+    "meaning": {
+      "properties": {
+        "description": {
+          "type": "string"
+        },
+        "energy": {
+          "enum": [
+            "waxing",
+            "waning",
+            "new",
+            "full"
+          ],
+          "type": "string"
+        },
+        "illumination": {
+          "type": "string"
+        },
+        "keywords": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "name": {
+          "type": "string"
+        },
+        "symbol": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "symbol",
+        "description",
+        "keywords",
+        "energy",
+        "illumination"
+      ],
+      "type": "object"
+    },
+    "phase": {
+      "type": "string"
+    },
+    "sign": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "phase",
+    "illumination",
+    "age",
+    "sign",
+    "degree",
+    "distance"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

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"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedInput schema / properties / compact / description

Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"Set 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."

Changed1 schema field changedAug 1, 2026
- changedInput schema / properties / timezone / example
```
Previous value: -0New value: +"America/New_York"
```

Changed2 schema fields changedJul 31, 2026

removedInput schema / properties / timezone / default
```
Removed value: -0
```

changedInput schema / properties / timezone / description

Previous value: -"IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours (e.g. -5 for EST, 1 for CET). IANA resolved to the DST-correct offset for the given date. Defaults to 0 (UTC)."New value: +"IANA name (e.g. \"America/New_York\", \"Europe/London\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\"). IANA resolved to the DST-correct offset for the given date. Defaults to 0 (UTC)."

Changed1 schema field changedJul 22, 2026

changedInput schema / properties / compact / description

Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."

Changed1 schema field changedJul 22, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}

Changed1 schema field changedJul 12, 2026

changedInput schema / properties / timezone / description

Previous value: -"Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. \"Asia/Kolkata\"). IANA resolved to the DST-correct offset for the given date. Defaults to 0 (UTC)."New value: +"IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours (e.g. -5 for EST, 1 for CET). IANA resolved to the DST-correct offset for the given date. Defaults to 0 (UTC)."

First observedJul 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The read-only and non-destructive nature is already encoded in annotations, so the description only needs to add context, and it does: it enumerates the returned data and phase-name vocabulary. It also surfaces the behavioral nuance that time matters because the Moon moves ~13 degrees per day, affecting phase precision. This aligns with annotations rather than contradicting them.

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?

At three sentences, the description is appropriately sized and opens with the core function before adding use-case context. The phase-name enumeration is somewhat verbose if the output schema already defines those values, but it remains useful for an agent to anticipate response values. There is no filler.

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 zero required parameters, 100% schema coverage, read-only annotations, and an output schema, the description does not need to explain return structure or safety. The description adds the user-facing intent and enough behavioral context (time sensitivity, returned values) for an agent to call it correctly. The main omission, sibling differentiation, is a usage-guideline issue rather than a callability gap.

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?

Every parameter has a full schema description with formats, defaults, enums, and examples, so schema coverage is 100%. The tool description mostly describes outputs rather than parameters; the one parameter-level insight (time affects precision) is already present in the time parameter's schema. Little additional parameter meaning is contributed by the description.

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 opening sentence states a clear verb and resource ('Get current moon phase') and lists exact return fields, including phase name, illumination, lunar age, zodiac sign, and distance. It is unambiguous about what the tool computes. It does not contrast itself with sibling moon-phase tools such as get_astrology_moon_phase_calendar_year_month or get_astrology_moon_phase_upcoming, so differentiation is left to the name/title.

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 final sentence names real consumer contexts ('moon tracking apps, lunar calendars, astrology widgets, gardening by moon phase tools'), which hints at applicable use cases. It does not say when to prefer this tool over the calendar/upcoming moon-phase siblings or provide any exclusions. Selection guidance is absent.

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

All Western Astrology MCP Server by RoxyAPI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?