Skip to main content
Glama
RoxyAPI

RoxyAPI Astrology MCP server

Official
by RoxyAPI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Astrocartography map - planetary lines and relocation calculator

post_astrology_astrocartography
Read-only

Generate an astrocartography map for any birth moment to plot planetary Midheaven, Imum Coeli, Ascendant, and Descendant lines for relocation astrology.

Instructions

Generate an astrocartography map of Midheaven, Imum Coeli, Ascendant, and Descendant planetary lines for any birth moment. Each line marks where a planet turns angular across the world, the core of relocation astrology and astro mapping. Returns right ascension, declination, the two meridian line longitudes, and sampled rising and setting curves ready to plot, with a short interpretation per line.

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
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
timeYesBirth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
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.
includeNoOptional comma separated list of extra bodies to plot beyond the ten classical planets. Allowed values: north-node, chiron, lilith. north-node is the mean lunar node. Unknown values are ignored. Defaults to none.
latitudeYesBirth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
nodeTypeNoLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass "mean" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to "true".true
timezoneYesTimezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.
longitudeYesBirth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.

Output Schema

NameRequiredDescriptionDefault
linesYes
summaryYes
birthDetailsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.2
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "1990-07-15",
-    "latitude": 40.7128,
-    "longitude": -74.006,
-    "time": "14:30:00",
-    "timezone": -5
-  }
-]New value: +[
+  {
+    "date": "1990-07-15",
+    "latitude": 40.7128,
+    "longitude": -74.006,
+    "time": "14:30:00",
+    "timezone": "America/New_York"
+  }
+]
    • changedInput schema / properties / timezone / example
      Previous value: --5New value: +"America/New_York"
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a safe read-only operation, so the bar is lower; the description adds useful context by disclosing the computation ('where a planet turns angular across the world') and what is shipped (right ascension, declination, meridian longitudes, sampled rising/setting curves, per-line interpretation). It says nothing about cost, rate limits, or caching, so it is not a 5.

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 sentences, front-loaded with the deliverable, then the meaning of the lines, then the return contents. Sizing is appropriate for the complexity, though the middle sentence is mildly decorative ('the core of relocation astrology') rather than actionable.

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?

With annotations covering the safety profile and a full output schema and 100% parameter coverage, the description only needs to establish purpose and output character, which it does. It could still say more about how the map is scoped (global coverage) and how optional flags like include/compact affect the result.

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% and the nine parameters (including enum-rich nodeType, lang, include, compact) are thoroughly documented in the schema itself. The description adds no parameter guidance beyond that, so the baseline of 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 and resource: generate an astrocartography map of MC/IC/Ascendant/Descendant planetary lines for a birth moment, and explains what each line means. It is clearly distinct in output from relocation_chart or local_space, but it never names or contrasts those siblings explicitly.

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 conveys what the artifact is for ('the core of relocation astrology and astro mapping') and that it takes any birth moment, which implies when it is wanted, but it gives no explicit when-to-use, prerequisites, or alternatives versus the relocation and local-space siblings.

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