Skip to main content
Glama
Sign In
RoxyAPI Astrology MCP server

RoxyAPI Astrology MCP server

Official
by RoxyAPI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get lunar calendar - Moon phases for entire month

get_astrology_moon_phase_calendar_year_month
Read-only

Retrieve daily moon phases and illumination for a specific month and year to create lunar calendars, moon planners, and astrology event schedules.

Instructions

Get complete lunar calendar showing moon phase and illumination for every day of a specific month. Perfect for creating moon phase calendars, lunar planners, and astrology event schedules.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": 2026,
      "month": 3
    },
    "name": "get_astrology_moon_phase_calendar_year_month"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
yearYesCalendar year, 1551 to 2649.
monthYesCalendar month (1-12). 1 = January, 12 = December.
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.

Output Schema

NameRequiredDescriptionDefault
yearYes
monthYes
calendarYes
monthNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.5
    • addedOutput schema / properties / calendar / items / properties / sign
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / calendar / items / required
      Previous value: -[
-  "date",
-  "phase",
-  "illumination"
-]New value: +[
+  "date",
+  "phase",
+  "illumination",
+  "sign"
+]
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description contributes scope information ('every day of a specific month', i.e., full-month coverage rather than a single date), but says nothing about response size, language fallback behavior, or the compact option's effect.

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?

Two sentences, front-loaded with the core capability, zero filler beyond a mildly promotional 'Perfect for' clause. Slightly expendable but not wasteful.

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?

An output schema exists, annotations cover safety, and schema coverage is complete, so the description only needs to nail purpose and scope — which it does. It could add a word on how it differs from the current/upcoming phase tools, but nothing essential for correct invocation 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%, so year, month, lang, and compact are all documented in the schema itself; baseline 3 applies. The description only reinforces that the month parameter yields per-day entries and adds no new detail on lang fallback or compact token savings.

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?

States a specific verb and resource: 'Get complete lunar calendar showing moon phase and illumination for every day of a specific month.' The monthly granularity implicitly separates it from the current/upcoming moon-phase siblings, but those siblings are never named, so differentiation is left to inference.

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 second sentence gives use cases ('moon phase calendars, lunar planners, astrology event schedules'), which implies when to reach for it, but there is no explicit when-not guidance or pointer to get_astrology_moon_phase_current / get_astrology_moon_phase_upcoming for single-day lookups.

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