MysticAPI

bodygraph

Compute an Energy Blueprint (Human Design) chart from a UTC birth instant. Returns type, authority, strategy, profile, definition, incarnation cross, channels, defined centers, and conscious/unconscious gate maps, plus a body-graph SVG. Location is NOT needed. Convert local birth time to UTC before calling. Costs 1 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": {
      "year": "<year>",
      "month": "<month>",
      "day": "<day>",
      "hour": "<hour>",
      "minute": "<minute>"
    },
    "name": "bodygraph"
  }
}

Input Schema

Name	Required	Description
`day`	Yes
`hour`	Yes	Hour 0-23 in UTC
`year`	Yes	4-digit year (UTC)
`month`	Yes
`minute`	Yes
`second`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 19, 2026
- changedInput schema / properties / hour / description
```
Previous value: -"Hour 0–23 in UTC"New value: +"Hour 0-23 in UTC"
```
First observedJul 7, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions the cost (1 call) and the return of an SVG, but does not disclose error behavior, rate limits, or whether it is read-only. Adequate but lacks depth.

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?

Three sentences: purpose/output summary, usage clarification (UTC, location not needed), and cost. No wasted words, efficiently front-loaded with essential information.

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?

Despite no output schema, the description lists many returned fields (type, authority, strategy, etc.) and an SVG, giving a solid mental model. It also provides necessary usage tips. Minor gap: no mention of error handling or input validation, but overall complete.

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 33% (hour and year have UTC explanations). The description adds context that parameters represent a UTC birth instant and that second is optional, partially compensating for low coverage, but could be more explicit about each parameter.

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 clearly states the tool computes an Energy Blueprint (Human Design) chart from a UTC birth instant, listing specific outputs like type, authority, strategy, etc. It distinguishes from sibling tools (ephemeris, numerology, etc.) by specifying Human Design and noting location is not needed.

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 explicitly instructs to convert local birth time to UTC before calling and notes that location is not needed, providing clear usage guidance. It does not explicitly mention when not to use or compare to siblings, but the context is sufficient.

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

All MysticAPI 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?