Skip to main content
Glama
Sign In
RoxyAPI Astrology MCP server

RoxyAPI Astrology MCP server

Official
by RoxyAPI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get upcoming moon phases - Next new moon, full moon, quarters

get_astrology_moon_phase_upcoming
Read-only

Retrieve upcoming New, First Quarter, Full, and Third Quarter Moon dates and phase names for lunar calendars, widgets, and astrology planning.

Instructions

Get upcoming moon phase transitions (New Moon, First Quarter Moon, Full Moon, Third Quarter Moon) for the next weeks/months. Returns dates and phase names for each lunar quarter. Perfect for lunar event calendars, moon phase widgets, and astrology planning tools.

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": {},
    "name": "get_astrology_moon_phase_upcoming"
  }
}

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
countNoNumber of upcoming moon phase transitions to return (1-20). Defaults to 8.
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.
startDateNoStart date in YYYY-MM-DD format. Defaults to today if omitted.

Output Schema

NameRequiredDescriptionDefault
phasesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 adds that results are phase names plus dates over a span of weeks/months, but says nothing about ordering, timezone/UTC handling of dates, or how the span relates to count — useful gaps remain.

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?

Three short sentences, front-loaded with what is returned and its scope, followed by use cases. Nothing is redundant or padded; only the marketing-flavored 'Perfect for' sentence is marginal.

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, so return-format detail is not required, and all four optional parameters are well documented with defaults. Combined with read-only annotations, an agent has enough to call it correctly; only the date/timezone semantics of the returned transitions are unaddressed.

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 lang, count, compact, and startDate are all fully documented in the schema itself, including ranges, defaults, and the compact columnar format. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 (get) and resource (upcoming moon phase transitions), enumerating the four phase types and the scope ('next weeks/months'). It reads clearly against siblings like get_astrology_moon_phase_current and get_astrology_moon_phase_calendar_year_month, but it never names those alternatives to sharpen the distinction.

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 description offers use-case framing ('lunar event calendars, moon phase widgets, astrology planning tools'), which implies usage. It does not say when to prefer this over the current-phase or month-calendar siblings, nor state any exclusions, so guidance is only implied.

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