Skip to main content
Glama
igmizo

auseklis

by igmizo

Compute Composite Chart

compute_composite_chart
Read-onlyIdempotent

Calculate a midpoint composite chart for two individuals to reveal the astrological signature of their relationship. Uses shorter-arc midpoints from each person's natal chart.

Instructions

Compute a midpoint composite chart for two people: a single chart describing the relationship itself, built from the shorter-arc midpoints of the two natal charts' positions and angles.

Both birth locations are required (the composite angles derive from each chart's Ascendant/Midheaven).

Example:

  • { datetime_a: "1990-03-15T15:45", timezone_a: "Europe/Riga", latitude_a: 56.95, longitude_a: 24.11, datetime_b: "1992-07-22T08:30", timezone_b: "America/New_York", latitude_b: 40.71, longitude_b: -74.01 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datetime_aYesPerson A's birth date and time.
timezone_aNoIANA 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.
latitude_aYesPerson A's birth latitude.
longitude_aYesPerson A's birth longitude.
datetime_bYesPerson B's birth date and time.
timezone_bNoIANA 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.
latitude_bYesPerson B's birth latitude.
longitude_bYesPerson B's birth longitude.
house_systemNoHouse system: whole-sign (default), equal, porphyry, or placidus.whole-sign
zodiacNoZodiac frame: tropical (Western default), sidereal-lahiri (Vedic), or sidereal-fagan-bradley (Western sidereal).tropical

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
zodiacYes
positionsYes
housesYes
aspectsYes
noteYes
Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint. The description adds behavioral context (composite angles derive from Ascendant/Midheaven) without contradicting 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?

The description is concise with a clear definition and an illustrative example, no superfluous text.

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?

Given the complexity and existence of output schema, the description covers the core functionality, requirements, and provides an example. It is sufficient for invocation.

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 description coverage is 100%, but the description adds value through an example showing exact parameter formats and emphasizing the requirement of both locations.

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 midpoint composite chart for two people, describing the relationship itself. It uses specific verb ('compute') and resource ('composite chart'), and the context of sibling tools like 'compute_synastry' implies differentiation.

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 indicates when to use (for two people) and notes that both birth locations are required. It provides an example but does not explicitly state when not to use or compare with alternatives like compute_synastry.

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