Skip to main content
Glama

explore_human_design

Read-onlyIdempotent

Generate a clickable Human Design Bodygraph to explore centers, gates, channels, Type, Profile, Authority, and Incarnation Cross.

Instructions

Generate an interactive Human Design Bodygraph with clickable centers, gates, and channels.

CREDIT COST: 4 credits where the bodygraph renders (2 for the chart + 2 for the visual), 2 in text-only hosts that skip the render. For chart data alone at 2 credits — including the activations, design, personality, strategy and variables this tool does not return — use human_design_chart.

Returns an embedded visual bodygraph explorer that lets you click any center or gate for instant Human Design interpretation. Shows defined/undefined centers, active gates, channels, Type, Profile, Authority, and Incarnation Cross. The chart is calculated using NASA JPL DE440 ephemerides for both Personality and Design positions. Use this instead of human_design_chart for a richer, interactive HD experience in MCP Apps-capable hosts (Claude Desktop). Falls back to a text summary in other hosts. Human Design was originated by Ra Uru Hu; OpenEphemeris is an independent calculation service, not affiliated with Jovian Archive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datetimeYesISO 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.
latitudeNoBirth 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.
locationNoBirth 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.
timezoneNoIANA 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.
longitudeNoBirth longitude in decimal degrees (positive = East). Optional if `location` is a place name.
Behavior5/5

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

Annotations already declare readOnly and idempotent, and the description adds significant behavioral context: credit costs vary by host, it falls back to text in non-capable hosts, and it explicitly notes 'this tool does not return' activations, design, personality, strategy, and variables. It also discloses the calculation source and non-affiliation, going well beyond annotations.

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 description is front-loaded with purpose and then economically covers credits, alternatives, fallback behavior, and limitations. It is longer than average but every sentence carries useful information; the only slight excess is the historical attribution to Ra Uru Hu, though it adds credibility.

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?

The description is complete for a tool with no output schema: it explains what is returned (interactive bodygraph with clickable interpretations), what the chart shows, when it falls back to text, and how costs differ. It also clarifies what it does not return, helping the agent avoid incorrect expectations.

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 schema already provides rich per-parameter guidance (e.g., time-sensitivity, location resolution, coordinate rules). The tool description adds little parameter-specific meaning beyond mentioning JPL DE440 ephemerides and 'both Personality and Design positions,' which is useful but not necessary given the schema's thoroughness.

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 opens with a specific verb and resource: 'Generate an interactive Human Design Bodygraph with clickable centers, gates, and channels.' It clearly distinguishes itself from sibling human_design_chart by emphasizing interactivity and richer visuals, making the tool's unique purpose unmistakable.

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

Usage Guidelines5/5

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

Explicit guidance is provided: 'Use this instead of human_design_chart for a richer, interactive HD experience in MCP Apps-capable hosts' and 'Falls back to a text summary in other hosts.' It also names the alternative for chart data alone (human_design_chart), specifying exactly when each tool should be chosen.

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