Skip to main content
Glama
openephemeris

Open Ephemeris

by openephemeris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Relocation Chart

ephemeris_relocation
Read-onlyIdempotent

Recast a natal chart for a new location, showing how houses and angles change while planetary longitudes stay the same. Use it to compare your chart across cities.

Instructions

Use this when the user asks 'how does my chart change if I move to London', 'what's my chart in Paris', 'my relocated Ascendant in Tokyo' or 'recast my chart for where I live now'. Returns the natal chart re-cast for a new location — the same planetary longitudes with the houses and angles that place gives them.

CREDIT COST: 1 credit per call.

Input Schema

NameRequiredDescriptionDefault
formatNo'llm' = compact.
timezoneNoIANA zone for a local datetime.
house_systemNoHouse system to use. Defaults to 'placidus'.
include_visualNoAlso return the relocated chart wheel as an image (+2 credits).
natal_datetimeYesISO 8601; zone required (`Z`/offset, or local time plus `timezone`).
natal_latitudeYesBirth latitude.
natal_longitudeYesBirth longitude.
relocation_latitudeYesNew-place latitude (+N).
relocation_longitudeYesNew-place longitude (+E).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv4.29.0
    • changedInput schema / properties / format / description
      Previous value: -"Output format. 'llm' = compact token-efficient output (available on all tiers)."New value: +"'llm' = compact."
    • changedInput schema / properties / natal_datetime / description
      Previous value: -"ISO 8601 datetime. A datetime with no zone is rejected; give a `Z` or ±HH:MM suffix, or a local time with the `timezone` argument. Date-only resolves to 12:00 UTC."New value: +"ISO 8601; zone required (`Z`/offset, or local time plus `timezone`)."
    • changedInput schema / properties / natal_latitude / description
      Previous value: -"Latitude of birth location in decimal degrees."New value: +"Birth latitude."
    • changedInput schema / properties / natal_longitude / description
      Previous value: -"Longitude of birth location in decimal degrees."New value: +"Birth longitude."
    • changedInput schema / properties / relocation_latitude / description
      Previous value: -"Latitude of the relocation city in decimal degrees (positive = North)."New value: +"New-place latitude (+N)."
    • changedInput schema / properties / relocation_longitude / description
      Previous value: -"Longitude of the relocation city in decimal degrees (positive = East)."New value: +"New-place longitude (+E)."
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone (e.g. `America/Chicago`); required when the datetime is naive, ignored otherwise."New value: +"IANA zone for a local datetime."
  2. Changed3 schema fields changedv4.24.2
    • addedInput schema / properties / include_visual
      Added value: +{
+  "description": "Also return the relocated chart wheel as an image (+2 credits).",
+  "type": "boolean"
+}
    • changedInput schema / properties / natal_datetime / description
      Previous value: -"ISO 8601 datetime; zone required — a `Z`/±HH:MM suffix or the `timezone` argument. Date-only resolves to 12:00 UTC. Full rule: server `instructions`."New value: +"ISO 8601 datetime. A datetime with no zone is rejected; give a `Z` or ±HH:MM suffix, or a local time with the `timezone` argument. Date-only resolves to 12:00 UTC."
    • changedInput schema / properties / natal_latitude / description
      Previous value: -"Latitude of birth location in decimal degrees. Resolve from a place name with location_search; never recall coordinates from memory."New value: +"Latitude of birth location in decimal degrees."
  3. Changed3 schema fields changedv4.8.0
    • changedInput schema / properties / natal_datetime / description
      Previous value: -"ISO 8601 birth datetime (local time at birth location)."New value: +"ISO 8601 datetime; zone required — a `Z`/±HH:MM suffix or the `timezone` argument. Date-only resolves to 12:00 UTC. Full rule: server `instructions`."
    • changedInput schema / properties / natal_latitude / description
      Previous value: -"Latitude of birth location in decimal degrees."New value: +"Latitude of birth location in decimal degrees. Resolve from a place name with location_search; never recall coordinates from memory."
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "IANA timezone (e.g. `America/Chicago`); required when the datetime is naive, ignored otherwise.",
+  "type": "string"
+}
  4. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description adds real value beyond them with the credit cost (1 credit per call) and the conceptual guarantee that longitudes are unchanged. It doesn't mention the +2 credit visual surcharge or any failure modes, which keeps it from 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.

Conciseness5/5

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

Two tight paragraphs: usage triggers first, then the return semantics, then cost. Every sentence carries information the agent needs and nothing is repeated from structured fields.

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 no output schema, the description does the necessary work of explaining what comes back (relocated houses and angles over the same longitudes). It leaves the concrete response shape and the visual-image option entirely to the schema, which is acceptable but leaves a small gap for a tool that can return an image.

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%, so the schema already documents all nine parameters including enums and coordinate signs. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource: re-casts the natal chart for a new location, and clarifies the invariant (same planetary longitudes, new houses/angles). This clearly separates it from ephemeris_natal_chart and ephemeris_house_cusps, which an agent might otherwise confuse it with.

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 trigger phrases ('how does my chart change if I move', 'relocated Ascendant in Tokyo') give concrete when-to-use conditions that map cleanly to user intent. It stops short of an explicit exclusion or naming an alternative for the plain natal case, so routing for edge cases is left to inference.

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