Skip to main content
Glama
igmizo

auseklis

by igmizo

Compute Natal Chart

compute_natal_chart
Read-onlyIdempotent

Compute a comprehensive natal chart with planetary positions, house cusps, aspects, and the Part of Fortune. Accepts local time in IANA timezone and supports tropical or sidereal zodiacs.

Instructions

Compute a complete natal (birth) chart: the ten classical bodies plus lunar nodes, Lilith, and Chiron, house cusps, Ascendant and Midheaven, the Part of Fortune, and all aspects.

Accepts local birth time directly when given the IANA timezone — no manual UTC conversion needed. Supports tropical (Western) and sidereal (Vedic/Lahiri, Fagan-Bradley) zodiacs.

Examples:

  • "Chart for 15 March 1990, 3:45pm in Riga" -> { datetime: "1990-03-15T15:45", timezone: "Europe/Riga", latitude: 56.95, longitude: 24.11 }

  • Vedic chart: add { zodiac: "sidereal-lahiri" }

Returns: positions (13 points), houses (12 cusps + angles), the Part of Fortune (classical day/night formula, with the dayChart flag showing which applied), aspects, and the ayanamsa applied (0 for tropical).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zodiacNoZodiac frame: tropical (Western default), sidereal-lahiri (Vedic), or sidereal-fagan-bradley (Western sidereal).tropical
datetimeYesBirth date and time.
latitudeYesGeographic latitude in degrees, positive north (-90 to 90).
timezoneNoIANA timezone the datetime is local to, e.g. "Europe/Riga" or "America/New_York". Omit when the datetime already carries Z or a UTC offset.
longitudeYesGeographic longitude in degrees, positive east (-180 to 180).
house_systemNoHouse system: whole-sign (default), equal, porphyry, or placidus.whole-sign

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
utcYes
housesYes
zodiacYes
aspectsYes
ayanamsaYes
locationYes
positionsYes
partOfFortuneYes
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value by detailing output components like the Part of Fortune formula and ayanamsa, but does not introduce new behavioral traits beyond what annotations suggest.

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 well-structured with a clear summary, details, and examples. It is front-loaded with the main purpose. While slightly long, every sentence conveys useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a natal chart and the presence of an output schema, the description thoroughly covers all input options, output components, and includes an example. It is fully adequate for an AI agent to understand and use the tool.

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?

Schema description coverage is 100%, so the baseline is 3. The description includes an example usage but does not add significant new meaning to individual parameters beyond what the schema provides.

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?

The description clearly states the tool computes a complete natal chart with specific bodies, house cusps, angles, Part of Fortune, and aspects. It distinguishes from siblings like compute_synastry by focusing on a single birth chart.

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

Usage Guidelines4/5

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

The description provides examples and explains how to input local time with IANA timezone, but does not explicitly state when to use this tool versus alternatives like compute_transits or compute_progressions. The sibling tool names implicitly differentiate the use cases.

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/igmizo/auseklis'

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