Skip to main content
Glama

human_design_chart

Read-only

Calculate a complete Human Design chart from birth date, time, and location. Get your Type, Strategy, Authority, Profile, defined/undefined Centers, activated Gates and Channels, Incarnation Cross, and personality/design planetary positions.

Instructions

Calculate a full Human Design I Ching hexagram chart from birth data. Returns the person's Type (Generator, Manifesting Generator, Projector, Manifestor, Reflector), Strategy, Authority, Profile (e.g. 1/3, 2/4), defined and undefined Centers, activated Gates and Channels, Incarnation Cross, and both Personality (conscious) and Design (unconscious) planetary positions.

CREDIT COST: 2 credits per call.

Human Design uses two calculation moments: the birth time (Personality) and ~88° of Sun motion before birth (~3 months prior, the Design calculation). The API handles this automatically.

IMPORTANT: The datetime should be in UTC. If you have local birth time, convert to UTC first.

EXAMPLE: Get the Human Design chart for someone born April 15, 1990 at 7:30 PM UTC: datetime='1990-04-15T19:30:00Z', latitude=41.8781, longitude=-87.6298

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datetimeYesISO 8601 birth datetime in UTC, e.g. '1990-04-15T19:30:00Z'. Must include 'Z' or timezone offset.
latitudeNoLatitude of birth location in decimal degrees (positive = North).
longitudeNoLongitude of birth location in decimal degrees (positive = East).
formatNoOutput format. 'llm' returns compact array projection for token efficiency (available on all tiers). 'json' returns verbose full output.
include_visualNoWhen true, renders the Human Design bodygraph as an SVG and embeds it in the response. The bodygraph image will display in the conversation alongside the data. Costs 2 additional credits on top of the base call cost.
visual_configNoOptional rendering preferences (only used when include_visual=true).
Behavior5/5

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

The description adds value beyond annotations by disclosing credit cost, automatic design calculation, and UTC requirement. It does not contradict the readOnlyHint or destructiveHint.

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 well-structured with paragraphs, bullet points, and an example. It conveys necessary information without redundancy.

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 complexity (6 params, nested objects) and no output schema, the description adequately explains what the tool returns and how to use it. Minor improvement could be listing all output fields explicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds contextual info like credit cost for include_visual and a detailed example, which aids understanding beyond schema descriptions.

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 calculates a full Human Design chart, lists returned elements (Type, Strategy, Authority, etc.), and distinguishes from sibling tools like human_design_bodygraph by focusing on chart calculation.

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 provides clear when-to-use guidance: for getting a Human Design chart from birth data. It includes important prerequisites like UTC conversion, credit cost, and an example, but does not explicitly mention when not to use or alternatives.

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