Skip to main content
Glama

Human Design MCP Server by RoxyAPI

Calculate the Human Design profile and line keynotes

post_human_design_profile
Read-only

Calculate the Human Design profile for a birth moment: the conscious Personality Sun line over the unconscious Design Sun line, with the keynote for each. The profile is the geometry of the life role, for example 5/1 the Heretic Investigator. Verified against NASA JPL Horizons positions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesBirth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.
langNoResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.en
timeYesBirth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.
compactNoSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
latitudeNoBirth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.
nodeTypeNoLunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass "mean" to match it. Defaults to "true".true
timezoneYesIANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.
longitudeNoBirth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read behavior is covered. The description adds the credibility detail 'Verified against NASA JPL Horizons positions,' which hints at computational rigor but not much about edge cases or failure. It does not contradict the annotations. Overall, it adds a small amount of behavioral context beyond the annotations.

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 two sentences and front-loaded with the primary purpose. It conveys the precise scope in the first sentence ('conscious Personality sun line over the unconscious Design Sun line'), then adds the profile-role example and the NASA verification in a compact, no-waste style. Every sentence earns its place.

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?

For a calculate-birth-profile tool with a rich input schema, the description provides the core output semantics (the profile line and keynote) and a real example. There is no output schema, so a bit more detail on the exact response shape could be useful, but the combination of the description and the fully described parameters is sufficient for most tool-invocation contexts. It does not list the full set of returned properties, but it captures what the profile means and how it's derived.

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?

The schema covers 100% of the parameters with detailed description texts, so a baseline of 3 is appropriate. The description contributes extra meaning by tying the parameters to the concept 'conscious Personality Sun line over the unconscious Design Sun line,' which is not directly stated in the schema. It also mirrors the example date/time in the schema, though it doesn't explain the language or compact options because the schema already does that fully.

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 starts with a specific verb and a concrete resource: 'Calculate the Human Design profile for a birth moment.' It clearly states the output (conscious Personality line over unconscious Design line, with keynotes) and the example '(5/1 the Heretic Investigator)' tautologically explains the concept. It separates this tool from the center/gate/number siblings by owning the profile calculation.

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

Usage Guidelines3/5

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

The description implies that an agent should use this tool whenever a birth moment's profile is needed, and the sibling list indicates alternatives for centers, gates, and numbering. However, it does not state explicit when-to-use or when-not-to-use conditions or name an alternative. The wording is 'the profile is the geometry of the life role,' which gives context, but no contrast or exclusion is provided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

The static reference tools are clearly distinct, and connection, transit, and penta handle unique types of analysis. However, the full bodygraph endpoint already returns type, profile, centers, gates, and channels, so the component-specific calculation endpoints create moderate selection ambiguity.

Naming Consistency4/5

The tools follow a clear post_human_design_ / get_human_design_ pattern, with get_ reserved for reference lookups and post_ used for calculations. The pattern is slightly inconsistent because the two reference tools add _id and _number suffixes, while the calculation tools use plain plural resource names.

Tool Count4/5

Twelve tools is within a reasonable scope and covers the broad Human Design domain, including basic charts, transit, compatibility, and group analysis. The count is slightly higher than strictly necessary because several partial-looking endpoints duplicate the data already returned by the full bodygraph endpoint.

Completeness5/5

The server covers the full core chart generation flow, reference data for centers and gates, profile, type, variables, transit overlays, connection charts, and group connections. There are no obvious dead ends for Human Design apps and a reading or coaching workload seems well supported.

Resources