RoxyAPI Astrology MCP server

Official

by RoxyAPI

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Astrocartography map - planetary lines and relocation calculator

post_astrology_astrocartography

Read-only

Generate astrocartography maps marking where planets turn angular worldwide for any birth moment, returning Midheaven, Imum Coeli, Ascendant and Descendant lines with coordinates and interpretations.

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

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
`lang`	No	Response 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
`time`	Yes	Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
`compact`	No	Set 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.
`include`	No	Optional 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.
`latitude`	Yes	Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
`nodeType`	No	Lunar 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
`timezone`	Yes	Timezone: 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.
`longitude`	Yes	Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`lines`	Yes
`summary`	Yes
`birthDetails`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the tool read-only and non-destructive, so the description does not need to cover safety. It adds behavioral context by describing exactly what the map returns (right ascension, declination, meridian longitudes, sampled curves, interpretation), which goes beyond the raw readOnlyHint. This helps the agent anticipate output shape and purpose without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences with no filler: the first sentence states the core action, the second gives context/meaning, and the third lists the return contents. Each sentence earns its place, and the primary verb is front-loaded. It is informative without being verbose.

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?

Given the tool's complexity (9 parameters, output schema present), the description efficiently covers the core behavior, the output format, and the interpretive component ('short interpretation per line'). It does not elaborate on edge cases or alternatives, but the schema and annotations already carry that weight. The missing differentiation from close siblings is a minor gap in an otherwise complete picture.

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 each parameter (date, time, latitude, longitude, timezone, include, nodeType, lang, compact) already has detailed semantic descriptions. The tool description adds no parameter-level meaning beyond the general 'birth moment' phrase. With full schema coverage, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise verb ('Generate') and a specific resource ('astrocartography map of Midheaven, Imum Coeli, Ascendant, and Descendant planetary lines'). It further explains what the lines represent ('where a planet turns angular'), which separates it from generic relocation charts or other astrology maps. The level of detail makes the tool's purpose unmistakable without needing to open the schema.

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 explanation that this is 'the core of relocation astrology and astro mapping' implies when it should be used, but no alternatives are named and no exclusion criteria are given. Sibling tools like post_astrology_relocation_chart or post_astrology_local_space are not mentioned, so the agent must infer relative fit from the description alone. That meets the 'implied usage' bar, not explicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server