Calculate a complete Human Design bodygraph (natal chart) for a birth moment.
Plan: Standard or higher · Cost: 1 credit per call.
| Name | Required | Description | Default |
|---|---|---|---|
| verbose | No | ||
| birth_datetime | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
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.
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.
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.
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.
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.
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.
Add one secure layer between your agents and this server.
Each tool targets a distinct type of calculation (bodygraph, composite, dreamrave, penta, transit, location search) with no overlap, making it easy for an agent to select the correct one.
Most tools follow a 'calculate_' pattern, but 'get_transit' and 'search_locations' break the pattern, introducing inconsistency. While the verbs are descriptive, the lack of uniformity may confuse agents.
With 6 tools, the server is well-scoped for a Human Design calculation API—covering all major chart types and a helper function without superfluous tools.
The tool set covers all primary Human Design calculations (individual, composite, dreamrave, penta, transit) and location lookup. Missing are tools for interpreting or persisting results, but core calculations are complete.
