Skip to main content
Glama
Sign In
astroway-mcp

astroway-mcp

Official
by astroway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Penta Chart

astroway_hd_penta
Read-onlyIdempotent

Calculate a Penta group chart for 3–5 people, combining their BodyGraphs to reveal group dynamics and collective conditioning.

Instructions

Calculate the Penta (group) chart for 3–5 people: combined BodyGraph showing group dynamics and collective conditioning.

[Group: Human Design] [Endpoint: POST /v1/hd/penta] [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_penta"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes

Output Schema

NameRequiredDescriptionDefault
roleNo
sizeNo
channelsNo
definedCentersNo
pentaAuthorityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • 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."
  2. Addedv1.6.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds operationally relevant context not found there: the POST endpoint, the required 'inputs' payload, and a concrete cost of 100 credits (Tier 4). It stops short of describing error behavior or how the group chart is assembled, but the cost and endpoint disclosure is genuinely useful beyond the annotations.

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?

A single front-loaded sentence gives the purpose and scope, followed by compact bracketed metadata for group, endpoint, required field and cost. Nothing is redundant or padded.

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?

An output schema exists, so return values need not be explained, and the input schema documents the per-person fields in depth. The remaining gap is differentiation from closely related group/synastry tools, which the description leaves unaddressed.

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 description adds only '[Required: inputs]' and the 3–5 person cardinality, both of which are already expressed by the schema's minItems/maxItems and required array. The nested schema itself is richly documented (timezone, ayanamsa, houseSystem, timezoneOffset), so the description relies on the schema doing the heavy lifting.

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 the Penta (group) chart') and pins the scope to 3–5 people producing a combined BodyGraph, which is far more than a restatement of the name. It does not explicitly distinguish itself from the sibling astroway_hd_group_overlay, so an agent must still infer which group-chart tool to pick.

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

Usage Guidelines3/5

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

The '3–5 people' scope gives an implicit usage condition, and the group/collective-conditioning framing hints at when the tool is appropriate. However, there is no explicit when-to-use versus when-not-to-use guidance and no named alternative among the many Human Design siblings.

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

Deploy Server

Other Tools