astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Relocation Chart

astroway_geo_relocation

Read-onlyIdempotent

Recalculate a natal chart for a new geographic location, returning updated house cusps and planet house positions from the same birth moment.

Instructions

Recalculate a natal chart for a new geographic location (same birth moment, different lat/lng). Returns new houses and planet house positions.

[Group: Astro-Geography] [Endpoint: POST /v1/relocation] [Cost: 50 credits (Tier 3)]

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

Input Schema

Name	Required	Description	Default
`body`	Yes	Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.

Output Schema

Name	Required	Description	Default
`delta`	No
`natal`	No
`relocated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.1Nov 9, 2026

changedInput schema / properties / body / allOf

Previous value: -[
-  {
-    "description": "Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.",
-    "properties": {
-      "natal": {
-        "additionalProperties": {
-          "anyOf": [
-            {},
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "description": "Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems.",
-        "properties": {
-          "ayanamsa": {
-            "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
-            "enum": [
-              "fagan-bradley",
-              "lahiri",
-              "de-luce",
-              "raman",
-              "krishnamurti",
-              "kp",
-              "yukteshwar",
-              "jn-bhasin",
-              "true-citra",
-              "djwhal-khul"
-            ],
-            "type": "string"
-          },
-          "ayanamsaId": {
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "city": {
-            "default": "",
-            "type": "string"
-          },
-          "cosmogram": {
-            "type": "boolean"
-          },
-          "date": {
-            "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-            "type": "string"
-          },
-          "houseSystem": {
-            "default": "P",
-            "enum": [
-              "P",
-              "K",
-              "R",
-              "C",
-              "E",
-              "W",
-              "B",
-              "M",
-              "O",
-              "A",
-              "T",
-              "V",
-              "D",
-              "F",
-              "G",
-              "H",
-              "I",
-              "i",
-              "L",
-              "N",
-              "Q",
-              "S",
-              "U",
-              "X",
-              "Y"
-            ],
-            "type": "string"
-          },
-          "latitude": {
-            "maximum": 90,
-            "minimum": -90,
-            "type": "number"
-          },
-          "longitude": {
-            "maximum": 180,
-            "minimum": -180,
-            "type": "number"
-          },
-          "name": {
-            "default": "",
-            "type": "string"
-          },
-          "time": {
-            "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
-            "type": "string"
-          },
-          "timezone": {
-            "description": "IANA 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.",
-            "type": "string"
-          },
-          "timezoneOffset": {
-            "anyOf": [
-              {
-                "maximum": 14,
-                "minimum": -14,
-                "type": "number"
-              },
-              {
-                "type": "null"
-              }
-            ],
-            "default": 0,
-            "description": "Hours 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."
-          },
-          "zodiacType": {
-            "enum": [
-              "tropical",
-              "sidereal"
-            ],
-            "type": "string"
-          }
-        },
-        "required": [
-          "date",
-          "time",
-          "latitude",
-          "longitude"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "natal"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "target": {
-        "properties": {
-          "city": {
-            "type": "string"
-          },
-          "latitude": {
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "longitude": {
-            "type": [
-              "number",
-              "null"
-            ]
-          }
-        },
-        "required": [
-          "latitude",
-          "longitude"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "target"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "description": "Wrapper { natal: ChartInput } used by endpoints that take a base natal plus extra parameters in flat fields.",
+    "properties": {
+      "natal": {
+        "additionalProperties": {
+          "anyOf": [
+            {},
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "description": "Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems.",
+        "properties": {
+          "ayanamsa": {
+            "description": "Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.",
+            "enum": [
+              "fagan-bradley",
+              "lahiri",
+              "de-luce",
+              "raman",
+              "krishnamurti",
+              "kp",
+              "yukteshwar",
+              "jn-bhasin",
+              "true-citra",
+              "djwhal-khul"
+            ],
+            "type": "string"
+          },
+          "ayanamsaId": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "city": {
+            "default": "",
+            "type": "string"
+          },
+          "cosmogram": {
+            "type": "boolean"
+          },
+          "date": {
+            "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+            "type": "string"
+          },
+          "houseSystem": {
+            "default": "P",
+            "enum": [
+              "P",
+              "K",
+              "R",
+              "C",
+              "E",
+              "W",
+              "B",
+              "M",
+              "O",
+              "A",
+              "T",
+              "V",
+              "D",
+              "F",
+              "G",
+              "H",
+              "I",
+              "i",
+              "L",
+              "N",
+              "Q",
+              "S",
+              "U",
+              "X",
+              "Y"
+            ],
+            "type": "string"
+          },
+          "latitude": {
+            "maximum": 90,
+            "minimum": -90,
+            "type": "number"
+          },
+          "longitude": {
+            "maximum": 180,
+            "minimum": -180,
+            "type": "number"
+          },
+          "name": {
+            "default": "",
+            "type": "string"
+          },
+          "time": {
+            "pattern": "^\\d{2}:\\d{2}(:\\d{2})?$",
+            "type": "string"
+          },
+          "timezone": {
+            "description": "IANA 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.",
+            "type": "string"
+          },
+          "timezoneOffset": {
+            "anyOf": [
+              {
+                "maximum": 14,
+                "minimum": -14,
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": 0,
+            "description": "Hours 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."
+          },
+          "zodiacType": {
+            "enum": [
+              "tropical",
+              "sidereal"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "date",
+          "time",
+          "latitude",
+          "longitude"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "natal"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "target": {
+        "properties": {
+          "city": {
+            "type": "string"
+          },
+          "latitude": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "longitude": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "latitude",
+          "longitude"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "target"
+    ],
+    "type": "object"
+  }
+]

Addedv1.6.0Oct 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-structured behavior: the endpoint is POST /v1/relocation and each call costs 50 credits (Tier 3), which matters for an agent deciding whether to call repeatedly, plus a note on what the result contains.

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?

The opening sentence is front-loaded with the operation and its defining constraint, followed by the return summary; every clause earns its place. The trailing bracketed metadata block is slightly mechanical but compact and useful.

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 values need not be spelled out, and the description still summarizes them in one line. Endpoint, cost and group are provided, leaving little an agent needs to know before invoking a read-only computation with a fully documented schema.

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 nested natal/target schemas are heavily documented, so the baseline of 3 applies. The description only adds the implicit relationship that the natal block must carry the original birth moment while the target carries the new coordinates; it gives no field-level detail beyond the schema.

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 specific verb and resource: 'Recalculate a natal chart for a new geographic location', and adds the crucial scope qualifier 'same birth moment, different lat/lng', which pins down the relocation-chart semantics. It does not name the closest sibling (astroway_reports_relocation), so a mild ambiguity remains about which relocation-family tool to pick, but the operation itself is unambiguous.

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 phrase 'same birth moment, different lat/lng' implies when this tool applies (a relocation chart rather than a fresh natal chart), which is real guidance. However, there is no explicit when-not-to-use statement and no pointer to alternatives such as astroway_reports_relocation or astroway_geo_acg, leaving the agent to infer the choice.

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

Deploy Server