Skip to main content
Glama

ephemeris_relocation

Read-only

Calculate how moving to a new city shifts your house placements and angles by re-casting your natal chart for a different location, keeping planetary longitudes unchanged.

Instructions

Calculate a relocation chart — the same natal planetary positions re-cast for a different geographic location. Used to understand how living in a different city shifts house placements and angles, without changing the planetary longitudes in the chart.

CREDIT COST: 1 credit per call.

EXAMPLE: How does moving from Chicago to London change someone's chart? natal_datetime='1990-04-15T14:30:00', natal_latitude=41.8781, natal_longitude=-87.6298, relocation_latitude=51.5074, relocation_longitude=-0.1278

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
natal_datetimeYesISO 8601 birth datetime (local time at birth location).
natal_latitudeYesLatitude of birth location in decimal degrees.
natal_longitudeYesLongitude of birth location in decimal degrees.
relocation_latitudeYesLatitude of the relocation city in decimal degrees (positive = North).
relocation_longitudeYesLongitude of the relocation city in decimal degrees (positive = East).
house_systemNoHouse system to use. Defaults to 'placidus'.
formatNoOutput format. 'llm' = compact token-efficient output (available on all tiers).
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description adds credit cost information ('CREDIT COST: 1 credit per call') and clarifies behavioral nuance: 'without changing the planetary longitudes in the chart.' No contradictions.

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 concise: two short paragraphs plus an example. Each sentence adds value—purpose, usage, credit cost, and a clear example. No fluff.

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 lack of output schema, the description could specify return details (e.g., house cusps, angles). It mentions 'house placements and angles' but does not describe the output structure. With moderate complexity (7 params), it is mostly complete but lacks output specifics.

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 coverage is 100%, providing baseline meaning for all parameters. The description adds value through an example that demonstrates correct usage of natal and relocation coordinates, but does not elaborate further on parameters like house_system or format beyond what the schema provides.

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 clearly states the tool's purpose: 'Calculate a relocation chart — the same natal planetary positions re-cast for a different geographic location.' It distinguishes itself from sibling ephemeris tools by focusing specifically on relocation, with a unique verb-resource pairing.

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 explains when to use the tool: 'Used to understand how living in a different city shifts house placements and angles.' It provides a concrete example contrasting Chicago and London, but does not explicitly state when not to use it or compare with alternatives like ephemeris_overlay.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openephemeris/openephemeris-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server