Human Design API (Human Design Hub)

calculate_bodygraph

Calculate a complete Human Design bodygraph (natal chart) for a birth moment.

Plan: Standard or higher · Cost: 1 credit per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "birth_datetime": "<birth_datetime>"
    },
    "name": "calculate_bodygraph"
  }
}

Input Schema

Name	Required	Description	Default
`verbose`	No
`birth_datetime`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 29, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It only mentions cost (1 credit) but does not state whether the tool is read-only, requires authentication, or has side effects. It fails to provide safety or mutation context for a calculation operation.

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 two sentences: one for purpose and one for plan/cost. It is concise and front-loaded with the main action, but could include more details without becoming verbose. No unnecessary words are present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a Human Design bodygraph and the existence of an output schema, the description adequately states the tool's purpose and cost. However, it lacks prerequisites, error handling, and input formatting guidance. It is partially complete but has gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so the description must compensate. It mentions 'birth moment' for birth_datetime but does not describe the format or the 'verbose' boolean. No parameter details beyond the names are provided, leaving the agent uninformed about expected input formats.

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 'Calculate a complete Human Design bodygraph (natal chart) for a birth moment.' It specifies the verb (calculate), resource (bodygraph), and scope (natal chart, birth moment). The tool name itself distinguishes it from siblings like calculate_composite and calculate_dreamrave, though no explicit differentiation is provided.

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

Usage Guidelines2/5

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

The description mentions 'Plan: Standard or higher · Cost: 1 credit per call,' which provides pricing and plan requirements but does not specify when to use this tool versus alternatives like calculate_composite or get_transit. No guidance on prerequisites or exclusions is given.

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

All Human Design API (Human Design Hub) 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?