Skip to main content
Glama
Sign In

Human Design MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Calculate Human Design connection chart - Two-person composite bodygraph compatibility

post_human_design_connection
Read-only

Calculate a Human Design connection chart by overlaying two bodygraphs. For each of the 36 channels the dynamic between the two people is classified as electromagnetic, dominance, compromise, or companionship, the four mechanics of how two designs meet. Returns every active gate for each person, including hanging gates, the nine centers as defined or open in the combined bodygraph with which person defines each, the combined definition, and a count of each dynamic. Built for relationship, dating, and coaching tools.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "personA": {
        "date": "1990-07-15",
        "time": "13:00:00",
        "timezone": "America/New_York"
      },
      "personB": {
        "date": "1990-07-15",
        "time": "13:00:00",
        "timezone": "America/New_York"
      }
    },
    "name": "post_human_design_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
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.
personAYesBirth moment of the first person in the connection.
personBYesBirth moment of the second person in the connection.

Output Schema

NameRequiredDescriptionDefault
centersYes
summaryYes
channelsYes
personAGatesNo
personBGatesNo
totalChannelsYes
combinedDefinitionYes
combinedDefinitionLocalizedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / personAGates
      Added value: +{
+  "items": {
+    "maximum": 64,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / personBGates
      Added value: +{
+  "items": {
+    "maximum": 64,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "centers": {
+      "items": {
+        "properties": {
+          "defined": {
+            "type": "boolean"
+          },
+          "definedBy": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "nameLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "defined",
+          "definedBy"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "channels": {
+      "items": {
+        "properties": {
+          "centers": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "circuit": {
+            "type": "string"
+          },
+          "circuitLocalized": {
+            "type": "string"
+          },
+          "dynamic": {
+            "type": "string"
+          },
+          "dynamicLocalized": {
+            "type": "string"
+          },
+          "gateA": {
+            "type": "number"
+          },
+          "gateB": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "nameLocalized": {
+            "type": "string"
+          },
+          "personAGates": {
+            "items": {
+              "type": "number"
+            },
+            "type": "array"
+          },
+          "personBGates": {
+            "items": {
+              "type": "number"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "gateA",
+          "gateB",
+          "name",
+          "circuit",
+          "centers",
+          "dynamic",
+          "personAGates",
+          "personBGates"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "combinedDefinition": {
+      "type": "string"
+    },
+    "combinedDefinitionLocalized": {
+      "type": "string"
+    },
+    "summary": {
+      "properties": {
+        "companionship": {
+          "type": "number"
+        },
+        "compromise": {
+          "type": "number"
+        },
+        "dominance": {
+          "type": "number"
+        },
+        "electromagnetic": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "electromagnetic",
+        "dominance",
+        "compromise",
+        "companionship"
+      ],
+      "type": "object"
+    },
+    "totalChannels": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "totalChannels",
+    "channels",
+    "centers",
+    "combinedDefinition",
+    "summary"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / personA / properties / timezone / description
      Previous value: -"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."New value: +"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 offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error."
    • changedInput schema / properties / personB / properties / timezone / description
      Previous value: -"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."New value: +"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 offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error."
  4. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"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."
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]
  5. Changed2 schema fields changed
    • changedInput schema / properties / personA / properties / nodeType / description
      Previous value: -"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 can move a node gate and, rarely, change the completed channels and therefore the type, authority or definition. If another calculator shows a different type, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\"."New value: +"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\"."
    • changedInput schema / properties / personB / properties / nodeType / description
      Previous value: -"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 can move a node gate and, rarely, change the completed channels and therefore the type, authority or definition. If another calculator shows a different type, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\"."New value: +"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\"."
  6. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "personA": {
+      "date": "1990-07-15",
+      "time": "13:00:00",
+      "timezone": "America/New_York"
+    },
+    "personB": {
+      "date": "1990-07-15",
+      "time": "13:00:00",
+      "timezone": "America/New_York"
+    }
+  }
+]
    • changedInput schema / properties / compact / description
      Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"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."
  7. Changed2 schema fields changed
    • changedInput schema / properties / personA / properties / nodeType / description
      Previous value: -"Lunar node convention for the North and South Node activations. Leave unset (or \"true\") for the standard Human Design chart: \"true\" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass \"mean\" to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass \"mean\" to match it."New value: +"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 can move a node gate and, rarely, change the completed channels and therefore the type, authority or definition. If another calculator shows a different type, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\"."
    • changedInput schema / properties / personB / properties / nodeType / description
      Previous value: -"Lunar node convention for the North and South Node activations. Leave unset (or \"true\") for the standard Human Design chart: \"true\" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass \"mean\" to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass \"mean\" to match it."New value: +"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 can move a node gate and, rarely, change the completed channels and therefore the type, authority or definition. If another calculator shows a different type, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\"."
  8. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."
  9. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}
  10. Changed2 schema fields changed
    • addedInput schema / properties / personA / properties / nodeType
      Added value: +{
+  "default": "true",
+  "description": "Lunar node convention for the North and South Node activations. Leave unset (or \"true\") for the standard Human Design chart: \"true\" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass \"mean\" to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass \"mean\" to match it.",
+  "enum": [
+    "mean",
+    "true"
+  ],
+  "example": "true",
+  "type": "string"
+}
    • addedInput schema / properties / personB / properties / nodeType
      Added value: +{
+  "default": "true",
+  "description": "Lunar node convention for the North and South Node activations. Leave unset (or \"true\") for the standard Human Design chart: \"true\" is the osculating node used by professional Human Design software (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against. Pass \"mean\" to match a calculator that uses the smoothed mean node (the traditional Western-astrology default, common in free chart tools). The two agree on almost every chart; they diverge by up to ~1.75 degrees only when a node sits on a gate boundary, where the choice can move a node gate and, rarely, change the completed channels and therefore the type, authority, or definition. If another calculator shows a different type, it is likely using the mean node: pass \"mean\" to match it.",
+  "enum": [
+    "mean",
+    "true"
+  ],
+  "example": "true",
+  "type": "string"
+}
  11. Changed6 schema fields changed
    • changedInput schema / properties / personA / properties / timezone / anyOf
      Previous value: -[
-  {
-    "maximum": 14,
-    "minimum": -14,
-    "type": "number"
-  },
-  {
-    "pattern": "^[A-Za-z_]+(?:\\/[A-Za-z0-9_+-]+){0,2}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 14,
+    "minimum": -14,
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / personA / properties / timezone / description
      Previous value: -"Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. \"America/New_York\", \"UTC\"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error."New value: +"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."
    • changedInput schema / properties / personA / properties / timezone / example
      Previous value: -5.5New value: +"America/New_York"
    • changedInput schema / properties / personB / properties / timezone / anyOf
      Previous value: -[
-  {
-    "maximum": 14,
-    "minimum": -14,
-    "type": "number"
-  },
-  {
-    "pattern": "^[A-Za-z_]+(?:\\/[A-Za-z0-9_+-]+){0,2}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 14,
+    "minimum": -14,
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / personB / properties / timezone / description
      Previous value: -"Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. \"America/New_York\", \"UTC\"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error."New value: +"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."
    • changedInput schema / properties / personB / properties / timezone / example
      Previous value: -5.5New value: +"America/New_York"
  12. First observed

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, so safety is covered. The description adds substantive domain behavior: the 36 channels are classified into electromagnetic, dominance, compromise, or companionship, and it enumerates what the response carries (active gates, hanging gates, center definitions with the defining person, combined definition, dynamic counts). It says nothing about auth, rate limits, or cost, but with annotations present this is a strong addition.

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?

Purpose is front-loaded in the opening clause, followed by computation semantics, return contents, and audience. The middle sentence is dense with lists but every element is informative. Only the closing audience sentence is arguably expendable.

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?

With an output schema present the description need not explain return values, yet it still names the key artifacts, and annotations cover the read-only profile, so the agent has enough to call this correctly. The remaining gap is routing guidance against the sibling chart tools, which the description leaves implicit.

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%, so the schema already documents personA/personB, timezone, nodeType, lang, and compact in detail. The description adds only the implicit notion that two birth moments are required and says nothing about the lang or compact parameters. Baseline 3 applies when the schema carries the load.

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?

States a specific verb and resource ('Calculate a Human Design connection chart by overlaying two bodygraphs') and immediately scopes it as a two-person composite, which cleanly separates it from the single-person post_human_design_bodygraph and the group-oriented post_human_design_penta siblings. The four dynamic classifications and the returned artifacts make the tool's output identity unmistakable.

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?

'Built for relationship, dating, and coaching tools' gives a domain context, but there is no explicit when-to-use versus the sibling tools (single bodygraph, penta for groups) and no prerequisites or exclusions. The agent can infer this is the two-person tool, but must do so from the purpose sentence rather than from 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 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources