Human Design MCP Server by RoxyAPI

Calculate the defined Human Design channels

post_human_design_channels

Read-only

Calculate the defined channels for a birth moment. A channel is defined when both of its gates are activated, and it wires together the two centers it connects. Returns each defined channel with its gates, name, circuit family, and connected centers, plus the full set of centers those channels define. Built for bodygraph rendering and definition analysis.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Birth 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.
`lang`	No	Response 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
`time`	Yes	Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.
`compact`	No	Set 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.
`latitude`	No	Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.
`nodeType`	No	Lunar 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
`timezone`	Yes	IANA 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.
`longitude`	No	Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful domain behavior: a channel is defined when both gates are activated and it wires the two centers together. It also states exactly what is returned, adding value 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences long and front-loads the action, then provides the definition rule and return contents. Each sentence earns its place, though the final 'Built for bodygraph rendering' is somewhat redundant with the earlier context.

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?

No output schema exists, so the description responsibly enumerates the returned data: gates, channel name, circuit family, connected centers, and the full defined center set. Combined with 100% schema coverage and read-only annotations, this gives the agent enough to call the tool correctly.

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 each parameter already has a rich description, especially timezone and nodeType. The tool description adds no parameter-specific details beyond what the schema provides, so the baseline 3 applies.

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?

The description clearly states a specific action ('Calculate the defined channels for a birth moment') and explains the core concept of a defined channel. It goes beyond the title by listing the returned contents, but it does not explicitly differentiate itself from sibling tools such as post_human_design_bodygraph.

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 gives a clear context: when channels are needed for a birth moment, especially for 'bodygraph rendering and definition analysis.' It does not mention alternatives or when not to use this tool, so it falls short of explicit exclusionary guidance.

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

All Human Design MCP Server by RoxyAPI tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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

Need Help?