Human Design MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_human_designC | Рассчитывает карту Human Design по дате, времени и месту рождения |
| get_human_design_definitionC | Получить определения и значения в Human Design |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one calculates a Human Design chart from birth data, while the other retrieves definitions and meanings. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun pattern (calculate_human_design and get_human_design_definition), using snake_case and clear action verbs that align with their functions.
With only two tools, the server feels thin for the Human Design domain, which typically involves multiple components like centers, gates, profiles, and types. A more comprehensive set would include tools for interpreting or analyzing specific aspects beyond just calculation and definitions.
The tool surface is significantly incomplete for Human Design. It lacks tools for key operations such as interpreting chart components (e.g., centers, channels), generating reports, or comparing charts, which are essential for practical use in this domain.