Skip to main content
Glama
astroway

astroway-mcp

Official

House Cusps

houses
Read-onlyIdempotent

Calculate house cusps, ascendant, and MC for any date, time, and location using Placidus, Koch, Whole Sign, Equal, and other systems. Automatically handles high-latitude quadrant systems.

Instructions

Standalone house calculation — 12 cusps + ascendant + MC + ARMC + vertex + co-asc + polar-asc. Supports Placidus, Koch, Regiomontanus, Campanus, Topocentric, Whole Sign, Equal, Porphyry, Morinus etc. Auto-fallback warning on |lat|>66.5° quadrant systems.

[Group: Calendar & Cycles] [Cost: 10 credits (Tier 1)]

Example request body: {"date":"1926-06-01","time":"09:30:00","timezoneOffset":-8,"latitude":34.0522,"longitude":-118.2437,"houseSystem":"P"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesBirth date YYYY-MM-DD
timeYesBirth time HH:mm:ss (local)
timezoneOffsetNoUTC offset in hours (e.g. 3 for UTC+3, -5 for EST)
latitudeNoBirth latitude in decimal degrees
longitudeNoBirth longitude in decimal degrees
houseSystemNoHouse system: P=Placidus (default), K=Koch, W=Whole Sign, E=Equal
cityNoCity name (display only)
Behavior4/5

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

Annotations already indicate read-only, idempotent behavior. The description adds value by disclosing the auto-fallback warning for extreme latitudes, a behavioral trait not covered by annotations.

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 description is concise, front-loads key information (outputs, systems), and includes group/cost metadata. However, it could be more structured with bullet points for readability.

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?

Without an output schema, the description lists expected outputs (cusps, ascendant, etc.). It also covers supported systems and edge-case behavior, making it reasonably complete for a standalone calculation tool.

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 descriptions for all 7 parameters. The description provides an example request body that illustrates how to use the parameters, adding practical value beyond the schema.

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?

Description clearly states it calculates house cusps and lists outputs. However, it does not explicitly differentiate from siblings like 'chart' which also includes house data, but the standalone nature is implied.

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 description provides a usage hint about auto-fallback for high latitudes, but lacks explicit guidance on when to use this tool versus alternatives (e.g., 'chart' or 'vedic_kp_cusps'). The context is implied but could be clearer.

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