astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

HD Group Overlay

astroway_hd_group_overlay

Read-onlyIdempotent

Calculate a combined Human Design group overlay chart for two or more people, revealing collectively defined centers and channels from their birth data.

Instructions

Calculate a combined HD group overlay chart for 2 or more people, showing collectively defined centers and channels.

[Group: Human Design] [Endpoint: POST /v1/hd/group-overlay] [Required: inputs] [Cost: 100 credits (Tier 4)]

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": {
      "inputs": "<inputs>"
    },
    "name": "astroway_hd_group_overlay"
  }
}

Input Schema

Name	Required	Description	Default
`inputs`	Yes

Output Schema

Name	Required	Description	Default
`count`	No
`openCenters`	No
`definedCenters`	No
`definedChannels`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.1Nov 9, 2026

changedInput schema / properties / inputs / items / description

Previous value: -"Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."New value: +"Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."

Addedv1.6.0Oct 24, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema behavior: the endpoint, that 'inputs' is required, and a cost of 100 credits (Tier 4), which lets an agent weigh whether to invoke it. It stops short of describing result shape or whether the collective overlay is deterministic across repeated calls, but the output schema covers returns.

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 purpose sentence is front-loaded and the bracketed metadata lines (group, endpoint, required, cost) are skimmable and each carries distinct information. Slightly more verbose than a pure one-liner, but no sentence is filler.

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?

With annotations and an output schema already supplied, the description only needs to cover purpose and routing, and it does the first adequately. It leaves out the upper bound of participants and any differentiation from the other multi-person HD tools, which matters given how many HD siblings exist.

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?

The single top-level parameter 'inputs' is explained only obliquely: '2 or more people' maps the array to one entry per person. The nested item schema is richly self-documenting (date/time formats, ayanamsa, timezone vs timezoneOffset, houseSystem), so the schema carries the semantics. The description is also slightly imprecise: it says '2 or more' while the schema caps the array at 10 items.

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?

States a specific verb and resource ('Calculate a combined HD group overlay chart') plus the output concept ('collectively defined centers and channels') and the input shape ('2 or more people'). It does not distinguish itself from close siblings such as astroway_hd_penta or astroway_hd_human_design_compatibility, which also involve multi-person HD analysis, so the agent gets a clear purpose but no routing signal.

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 phrase 'for 2 or more people' implies the applicable scenario and is the only usage constraint present. There is no statement of when to prefer this over the penta, compatibility, or synastry siblings, and no exclusion criteria, so the agent must infer selection from the name alone.

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

Deploy Server