Human Design MCP Server by RoxyAPI

Look up a Human Design gate by number

get_human_design_gates_number

Read-only

Look up the static reference data for a Human Design gate by its number from 1 to 64: the gate keynote name, the center it sits in, the matching I-Ching hexagram, and the gates that form a channel with it. A pure reference endpoint with no birth data required.

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": {
      "number": 34
    },
    "name": "get_human_design_gates_number"
  }
}

Input Schema

Name	Required	Description	Default
`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
`number`	Yes	Gate number from 1 to 64.
`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.

Output Schema

Name	Required	Description	Default
`name`	Yes
`center`	Yes
`number`	Yes
`centerName`	Yes
`nameLocalized`	No
`ichingHexagram`	Yes
`channelPartners`	Yes
`centerNameLocalized`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "center": {
+      "type": "string"
+    },
+    "centerName": {
+      "type": "string"
+    },
+    "centerNameLocalized": {
+      "type": "string"
+    },
+    "channelPartners": {
+      "items": {
+        "properties": {
+          "channel": {
+            "type": "string"
+          },
+          "channelLocalized": {
+            "type": "string"
+          },
+          "gate": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "gate",
+          "channel"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "ichingHexagram": {
+      "properties": {
+        "english": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "number",
+        "english"
+      ],
+      "type": "object"
+    },
+    "name": {
+      "type": "string"
+    },
+    "nameLocalized": {
+      "type": "string"
+    },
+    "number": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "number",
+    "name",
+    "center",
+    "centerName",
+    "ichingHexagram",
+    "channelPartners"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedSep 19, 2026
- addedInput schema / properties / number / maximum
```
Added value: +64
```
- addedInput schema / properties / number / minimum
```
Added value: +1
```
- changedInput schema / properties / number / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

Changed2 schema fields changedAug 25, 2026

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"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "number": 34
+  }
+]

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."

Changed1 schema field changedAug 2, 2026
- changedInput schema / properties / number / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```

Changed1 schema field changedJul 22, 2026

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."

Changed1 schema field changedJul 22, 2026

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"
+}

First observedJul 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With readOnlyHint=true and destructiveHint=false already set, the description adds useful behavioral context: the data is static reference, no birth data is required, and the endpoint is pure rather than computed. There is no contradiction and it supplements the annotations meaningfully, though it does not discuss things like localization fallback which the schema already covers.

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?

Two sentences, zero filler: the first packs the resource, scope, and return contents; the second gives the key usage signal. 'Static reference... no birth data required' earns its place by differentiating from chart-computation siblings.

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 simple read-only lookup tool with an output schema and fully documented parameters, the description covers what matters: what the gate lookup returns and that it is static/no-birth-data. It is slightly less explicit about when to choose it over get_human_design_centers_id, but the returned-domain enumeration makes the boundary clear enough.

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% (number, lang, compact are all documented), so the baseline applies. The description repeats the 1–64 range but does not add new parameter semantics beyond listing what the lookup returns, which is more relevant to the output than to the input parameters.

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-resource pair — 'Look up the static reference data for a Human Design gate by its number' — and enumerates the returned fields (keynote name, center, I-Ching hexagram, channel-forming gates). It also distinguishes itself from the post_* siblings by explicitly framing itself as a pure reference endpoint with no birth data required.

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?

It clearly signals the use case: static gate reference lookup independent of any birth chart data. This gives an agent enough context to prefer it over post_human_design_gates or bodygraph computations, though it does not name an alternative explicitly or state when not to use it.

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

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

Need Help?