RoxyAPI Astrology MCP server

Official

by RoxyAPI

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Generate relocation chart - Relocated birth chart calculator with shifted houses and angles

post_astrology_relocation_chart

Read-only

Calculate a relocated birth chart: natal planets keep their signs and degrees while houses and angles are recomputed for the new location.

Instructions

Calculate a relocation chart (relocated birth chart) for a new place on Earth. The birth moment stays the same, so every planet keeps its natal sign and degree, while the Ascendant, Midheaven, Vertex, and all twelve house cusps are recomputed for the new latitude and longitude. Returns the relocated houses and angles, the planets that change house, the angular planets activated at the new place, and the distance and compass direction from the birthplace. Built for relocation astrology readings, astrocartography style move planning, and travel charts. Verified against NASA JPL Horizons.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Birth date in YYYY-MM-DD format. The birth moment is unchanged by relocation, so this still defines the planetary positions of the chart.
`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. Combined with the timezone it fixes the exact birth instant, which the relocated angles and houses are recomputed for.
`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.
`timezone`	Yes	Birth timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York"). Resolved to the offset in force at the birth date and time. This is the birthplace timezone, not the new location timezone.
`houseSystem`	No	House system for dividing the relocated chart into 12 houses. Placidus (default) is time-sensitive and most popular in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.	placidus
`birthLatitude`	Yes	Birthplace latitude in decimal degrees (-90 to 90). Used for the original natal angles and houses that the relocated chart is compared against.
`birthLongitude`	Yes	Birthplace longitude in decimal degrees (-180 to 180). Positive East, negative West.
`relocationLatitude`	Yes	New location latitude in decimal degrees (-90 to 90). The relocated Ascendant and house cusps are most sensitive to north-south movement.
`relocationLongitude`	Yes	New location longitude in decimal degrees (-180 to 180). The relocated Midheaven shifts roughly one degree per degree of longitude moved.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`houses`	Yes
`vertex`	Yes
`changes`	Yes
`planets`	Yes
`ascendant`	Yes
`midheaven`	Yes
`relocation`	Yes
`houseSystem`	Yes
`birthDetails`	Yes
`interpretation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark the tool as readOnlyHint=true and destructiveHint=false, so no contradiction exists. The description adds useful behavioral nuances beyond annotations: the birth moment stays unchanged, planets keep natal signs and degrees, only angles and house cusps are recomputed, and results are 'Verified against NASA JPL Horizons.' This gives the agent confidence about the computation's scope and reliability.

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 compact yet information-dense, with every sentence earning its place: the core behavior, the computation details, the returned contents, and the target use cases. It is front-loaded with the main action and avoids redundant restatement of the tool name or title.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter tool with complete schema documentation and an output schema present, the description covers everything an agent needs to select and invoke it correctly: what it computes, what it returns, how it behaves relative to natal positions, and for which use cases it is intended. No critical gaps remain.

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 already has detailed descriptions, examples, formats, and constraints. The tool description adds a helpful conceptual framing (birth moment fixed, angles recomputed) but does not substantially enrich individual parameter meaning beyond the schema, so 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 states a precise verb and resource: 'Calculate a relocation chart (relocated birth chart)' for a new place on Earth, with an exact definition of what is recomputed and what stays fixed. It clearly distinguishes the tool from siblings like natal charts, astrocartography, and local space by emphasizing that planetary positions remain natal while only angles and house cusps shift.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool: 'Built for relocation astrology readings, astrocartography style move planning, and travel charts.' It does not explicitly name alternative sibling tools or state when not to use it, but the use cases are specific enough to guide an agent's selection.

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

Deploy Server