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.
| Name | Required | Description | Default |
|---|---|---|---|
| day | Yes | ||
| hour | Yes | Hour 0-23 in UTC | |
| year | Yes | 4-digit year (UTC) | |
| month | Yes | ||
| minute | Yes | ||
| second | No |
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.
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.
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.
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.
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.
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.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of mystical/astrological computation: human design chart, raw ephemeris, numerology, relationship composite, personal natal sky, and current sky overview. No two tools have overlapping purposes.
Tool names are single words or underscore-separated compounds (e.g., bodygraph, sky_personal), all lowercase and noun-like. While there's no verb_noun pattern, the naming is consistent in style and descriptive.
Six tools cover the core functionalities of a mystical API without being too few or too many. Each tool has a clear role, making the set well-scoped.
The tool set covers human design, ephemeris, numerology, relationships, and sky charts. Missing interpretive features like transit readings or detailed compatibility analysis, but core computation is present.