Skip to main content
Glama
Sign In
openephemeris

Open Ephemeris

by openephemeris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Interactive Human Design Bodygraph Explorer

explore_human_design
Read-onlyIdempotent

Calculate a Human Design bodygraph from birth date, time, and location to reveal Type, Profile, Authority, and Incarnation Cross with clickable centers, gates, and channels.

Instructions

Use this when the user asks 'what's my Human Design', 'am I a Generator / Projector / Manifestor / Reflector', 'show my bodygraph' or 'what's my strategy and authority'. Returns an interactive bodygraph (inline in Claude and ChatGPT; text summary elsewhere): centers, gates, channels, Type, Profile, Authority and Incarnation Cross, each clickable. Birthplace may be a place name (location).

CREDIT COST: 4 credits per call (2 chart + 2 render; +1 to resolve a place name). Human Design was originated by Ra Uru Hu; Open Ephemeris is an independent calculation service, not affiliated with Jovian Archive.

Input Schema

NameRequiredDescriptionDefault
datetimeYesISO 8601 with a required zone, or local time with `timezone`; minute-accurate.
latitudeNoBirth latitude (optional with `location`).
locationNoBirth place name, e.g. 'New York, NY'; geocoded. Give this or lat/lon.
timezoneNoIANA zone for a local birth time.
longitudeNoBirth longitude (optional with `location`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv4.29.0
    • changedInput schema / properties / datetime / description
      Previous value: -"ISO 8601 birth datetime in UTC, e.g. '1990-04-15T19:30:00Z'. Human Design is time-sensitive — accuracy to the minute matters. Must include 'Z' or a timezone offset."New value: +"ISO 8601 with a required zone, or local time with `timezone`; minute-accurate."
    • changedInput schema / properties / latitude / description
      Previous value: -"Birth latitude in decimal degrees (positive = North). Optional if `location` is a place name — the resolver fills it in. Takes decimal degrees, not a place name."New value: +"Birth latitude (optional with `location`)."
    • changedInput schema / properties / location / description
      Previous value: -"Birth location as a plain place name like 'New York, NY'; the server resolves it to coordinates and timezone (ambiguous names are rejected with a disambiguation hint). If neither location nor lat/lon is supplied the call is rejected."New value: +"Birth place name, e.g. 'New York, NY'; geocoded. Give this or lat/lon."
    • changedInput schema / properties / longitude / description
      Previous value: -"Birth longitude in decimal degrees (positive = East). Optional if `location` is a place name."New value: +"Birth longitude (optional with `location`)."
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone name for the birth location (e.g. 'America/New_York'). Used to convert a local birth time without a UTC offset to UTC for Personality and Design positions."New value: +"IANA zone for a local birth time."
  2. Changed4 schema fields changedv4.24.2
    • changedInput schema / properties / datetime / description
      Previous value: -"ISO 8601 birth datetime in UTC, e.g. '1990-04-15T19:30:00Z'. Human Design is time-sensitive — accuracy to the minute matters. Include 'Z' or a timezone offset."New value: +"ISO 8601 birth datetime in UTC, e.g. '1990-04-15T19:30:00Z'. Human Design is time-sensitive — accuracy to the minute matters. Must include 'Z' or a timezone offset."
    • changedInput schema / properties / latitude / description
      Previous value: -"Birth latitude in decimal degrees (positive = North). Optional if `location` is a place name — the resolver fills it in. Never recall coordinates from memory; either supply a place name or resolve with location_search first."New value: +"Birth latitude in decimal degrees (positive = North). Optional if `location` is a place name — the resolver fills it in. Takes decimal degrees, not a place name."
    • changedInput schema / properties / location / description
      Previous value: -"Birth location. Prefer a plain place name like 'New York, NY' — the server resolves it via the same lookup `location_search` uses (unambiguous names → coords + timezone; ambiguous names throw with a disambiguation hint). If neither location nor lat/lon is supplied the call is rejected — no more silent 0°N 0°E charts."New value: +"Birth location as a plain place name like 'New York, NY'; the server resolves it to coordinates and timezone (ambiguous names are rejected with a disambiguation hint). If neither location nor lat/lon is supplied the call is rejected."
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone name for the birth location (e.g. 'America/New_York'). Highly recommended for accuracy if providing local birth time without a UTC offset. Enables correct UTC conversion for precise Personality and Design positions."New value: +"IANA timezone name for the birth location (e.g. 'America/New_York'). Used to convert a local birth time without a UTC offset to UTC for Personality and Design positions."
  3. Addedv4.8.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description adds genuinely new behavior: rendering varies by host (inline in Claude and ChatGPT, text summary elsewhere), cost is 4 credits with +1 for geocoding, and provenance/affiliation is disclosed. It does not cover failure modes or accuracy caveats beyond the attribution line.

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?

Front-loads the use-when triggers, then the return value, then cost and attribution. All sentences are informative, though the credit/attribution block is dense and slightly front-loaded less prominently than the trigger phrases.

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?

With no output schema, the description does the necessary work of enumerating the returned fields and their interactive nature, and it discloses the location-vs-coordinates input path plus cost. Nothing an agent needs to invoke this correctly is missing.

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%, so the schema already documents datetime, latitude, longitude, location and timezone, including the 'give this or lat/lon' relationship. The description only restates the location convenience and adds the +1 credit note, which is marginal beyond structured data — baseline 3 is right.

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?

States a specific verb+resource ('Returns an interactive bodygraph') and enumerates the computed outputs: centers, gates, channels, Type, Profile, Authority, Incarnation Cross. It does not explicitly distinguish itself from the sibling human_design_chart or explore_human_design_transit/connection, though 'interactive' implies the differentiator.

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?

Gives concrete trigger utterances ('what's my Human Design', 'am I a Generator / Projector / Manifestor / Reflector', 'show my bodygraph') and a clear context (user asking about strategy and authority). No when-not or explicit routing to the non-interactive human_design_chart sibling, which keeps it short of a 5.

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