Western Moon Calendar
asterwise_get_western_moon_calendar
Returns lunar phase data for every day in a calendar month as a structured array. Each element is a complete daily phase object identical to asterwise_get_western_moon_phase.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
response_format | enum: markdown, json | no | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
year | integer/null | no | Four-digit calendar year, e.g. 2026. Defaults to the current year when omitted. |
month | integer/null | no | Month number 1-12. Defaults to the current month when omitted. |
What it covers
Month-at-a-glance lunar calendar for any year/month combination. Useful for building moon phase widgets, identifying full and new moon dates, planning tools based on lunar cycles, and content calendars. Defaults to the current month.
Workflow
BEFORE: None — standalone.
AFTER: None.
Input
year (optional int) — Target year. Defaults to current year. Example: 2026
month (optional int 1–12) — Target month. Defaults to current month.
Example: 5 (May)
Values outside 1–12 are rejected locally with MCP INVALID_PARAMS.
Output contract
data[] — array of daily phase objects, one per calendar day in the month.
Each object is identical to asterwise_get_western_moon_phase output.
Response format
response_format=json — array of daily phase objects.
response_format=markdown — month view with day-by-day phases.
Compute class
MEDIUM_COMPUTE (~500ms for 30 days)
Errors
INVALID_PARAMS (local):
— month outside 1–12 → MCP INVALID_PARAMS immediately.
INTERNAL_ERROR: Any upstream API failure → MCP INTERNAL_ERROR
Do not confuse with
asterwise_get_western_moon_phase — single-day phase only.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.