Skip to main content
Glama

AstroWay Core astrology

Moon Phase

astroway_calendar_moon_phase
Read-onlyIdempotent

Current moon phase at a given moment: illumination %, age in days, elongation, waxing/waning, sun + moon zodiac signs. Geocentric Sun-Moon elongation per Meeus Ch.48.

[Group: Calendar & Cycles] [Endpoint: POST /v1/moon-phase] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "time": "<time>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_calendar_moon_phase"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
cosmogramNo
longitudeYes
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
phaseNo
waxingNo
ageDaysNo
sunSignNo
moonSignNo
phaseNameNo
majorPhaseNo
sunLongitudeNo
elongationDegNo
moonLongitudeNo
illuminationPercentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed24 schema fields changed
    • removedInput schema / properties / ayanamsaId / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / ayanamsaId / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / ageDays / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / ageDays / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / elongationDeg / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / elongationDeg / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / illuminationPercent / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / illuminationPercent / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / majorPhase / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / majorPhase / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / moonLongitude / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / moonLongitude / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / moonSign / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / moonSign / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / phase / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / phase / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / phaseName / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / phaseName / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / sunLongitude / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / sunLongitude / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / sunSign / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / sunSign / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / waxing / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / waxing / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add genuine value beyond them: the cost ('10 credits (Tier 1)'), the concrete endpoint, and the underlying algorithm (Meeus Ch.48 geocentric Sun-Moon elongation), which tells an agent how precise the values are. It says nothing about error handling for invalid dates, whether latitude/longitude actually affect any returned field, or whether results are cached.

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 then a bracketed metadata block: front-loaded, scannable, and free of filler. The endpoint line is arguably redundant given structured transport data, but overall the wording is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 values need not be explained, yet with 15 parameters and a third of the schema undocumented the description leaves real ambiguity about which optional parameters are meaningful for a moon-phase call. It never clarifies the relationship to astroway_render_moon_phase or the lunar-calendar siblings, which is the main decision an agent must make.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% across 15 parameters, so the description is expected to compensate, and it does not. The '[Required: date, time, latitude, longitude]' line merely duplicates the schema's required list, and the many optional knobs (zodiacType, ayanamsa, ayanamsaId, houseSystem, cosmogram, city, name, fields, precision) are left unexplained — notably whether sidereal settings change the reported sun/moon zodiac signs.

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 description states a clear computation and resource ('current moon phase at a given moment') and enumerates the returned quantities (illumination %, age, elongation, waxing/waning, sun+moon signs), which is far more specific than the title. It does not, however, distinguish itself from near-neighbors such as astroway_render_moon_phase (image) or astroway_calendar_lunar_calendar, so an agent still has to infer which to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives. The '[Group: Calendar & Cycles]' tag only hints at domain, and the required-fields line is a restatement of the schema rather than usage advice.

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