Skip to main content
Glama
astroway

astroway-mcp

Official

Synastry House Overlay

synastry_house_overlay
Read-onlyIdempotent

Identify how each person's planets fall into the other's houses to reveal relationship dynamics and the most emphasized life areas.

Instructions

Locate each chart’s personal planets in the partner’s houses; reports top-3 emphasized houses on either side.

[Group: Comparisons] [Cost: 50 credits (Tier 3)]

Example request body: {"chart1":{"date":"1990-05-15","time":"14:30:00","timezoneOffset":3,"latitude":50.45,"longitude":30.52},"chart2":{"date":"1985-11-03","time":"08:15:00","timezoneOffset":2,"latitude":48.46,"longitude":35.04}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chart1YesBirth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss). Defaults to lat/lon/tz=0 if omitted; pass real values for accurate computation.
chart2YesBirth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss). Defaults to lat/lon/tz=0 if omitted; pass real values for accurate computation.
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety. Description adds behavioral detail that it reports top-3 emphasized houses, which is useful for agent understanding. No contradictions.

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?

Description is concise: one sentence for purpose, then group/cost, then example. Front-loaded and every sentence serves a purpose. No unnecessary words.

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?

Input schema is fully detailed, but description lacks output structure details (only mentions 'top-3 emphasized houses'). Given no output schema, more detail on return format would improve completeness for agent usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with per-parameter descriptions. Description does not add extra meaning beyond schema but provides an example request body that clarifies format and defaults, adding value beyond the schema.

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?

Description clearly states it locates personal planets in partner's houses and reports top-3 emphasized houses, with a specific verb and resource. It distinguishes from sibling tools like synastry and synastry_aspect_grid by focusing on house overlay.

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?

Description implies usage for house overlay analysis but does not explicitly state when to use vs alternatives like synastry or synastry_aspect_grid. No when-not or exclusions provided, only implied context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server