Skip to main content
Glama

Homo Universalis — Viveka Astrology, Natal Chart, Synastry, BaZi, Vedic, Mayan & Tarot MCP Oracle

calculate_7_wisdoms_seed_of_life

Read-onlyIdempotent

Compute a single person's deterministic natal chart, VVK-XXXX-YYYY Cosmic Soul Key, and 7-Wisdoms profile across Swiss Ephemeris astrology, Mayan Tzolkin, Vedic Jyotish, BaZi, I-Ching, Human Design, Tarot Major Arcana, and Kabbalah, plus current UTC transits in today_living_sky. Use this tool for one individual, or use calculate_3d_soul_synastry for two people and calculate_family_constellation_matrix for groups of 3 to 31 people. Zero-auth and stateless with no PII stored: soul_a is strictly deterministic for a given input while today_living_sky reflects the current UTC day. Omitting birth_time defaults to 12:00 UTC solar noon, providing tz converts local time to UTC for unequal Chaldean hours, omitting lat or lon drops Placidus houses and Ascendant, and invalid ISO dates return a structured JSON error.

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": {
      "birth_date": "<birth_date>"
    },
    "name": "calculate_7_wisdoms_seed_of_life"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoOptional IANA timezone name (e.g. 'Europe/Madrid', 'Asia/Tokyo') to convert local `birth_time` to UTC and compute unequal Chaldean planetary hours.
latNoOptional birth latitude in decimal degrees (-90 to 90, e.g. 41.3874); required together with `lon` for Placidus houses and Ascendant/MC.
lonNoOptional birth longitude in decimal degrees (-180 to 180, e.g. 2.1686); required together with `lat` for Placidus houses and Ascendant/MC.
langNoOutput language for localized archetype names and poetic narrative ('es' Spanish, 'en' English, or 'ca' Catalan).es
birth_dateYesISO birth date in YYYY-MM-DD format (e.g. '2000-03-20'). Required for all calculations.
birth_timeNoOptional birth time in HH:MM 24-hour format (e.g. '14:30'); defaults to '12:00' UTC when omitted.

Output Schema

NameRequiredDescriptionDefault
soul_aYes
today_living_skyNo
sister_ai_covenantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / birth_date / description
      Previous value: -"ISO birth date in YYYY-MM-DD format (e.g. '1980-05-24'). Required for all calculations."New value: +"ISO birth date in YYYY-MM-DD format (e.g. '2000-03-20'). Required for all calculations."
  2. Changed6 schema fields changed
    • changedInput schema / properties / birth_date / description
      Previous value: -"ISO birth date YYYY-MM-DD (e.g. '1980-05-24')"New value: +"ISO birth date in YYYY-MM-DD format (e.g. '1980-05-24'). Required for all calculations."
    • changedInput schema / properties / birth_time / description
      Previous value: -"Optional UTC birth time HH:MM (e.g. '14:30') for exact Moon degree, BaZi Hour Pillar, and Ascendant/MC"New value: +"Optional birth time in HH:MM 24-hour format (e.g. '14:30'); defaults to '12:00' UTC when omitted."
    • changedInput schema / properties / lang / description
      Previous value: -"Language for the localized poetic narrative ('es', 'en', or 'ca')"New value: +"Output language for localized archetype names and poetic narrative ('es' Spanish, 'en' English, or 'ca' Catalan)."
    • changedInput schema / properties / lat / description
      Previous value: -"Optional birth latitude (e.g. 41.3874 for Barcelona) for Ascendant, Midheaven (MC), and 12 Placidus houses"New value: +"Optional birth latitude in decimal degrees (-90 to 90, e.g. 41.3874); required together with `lon` for Placidus houses and Ascendant/MC."
    • changedInput schema / properties / lon / description
      Previous value: -"Optional birth longitude (e.g. 2.1686 for Barcelona) for Ascendant, Midheaven (MC), and 12 Placidus houses"New value: +"Optional birth longitude in decimal degrees (-180 to 180, e.g. 2.1686); required together with `lat` for Placidus houses and Ascendant/MC."
    • changedInput schema / properties / tz / description
      Previous value: -"Optional IANA timezone name (e.g. 'Europe/Madrid', 'Asia/Tokyo', 'Pacific/Auckland') for civil birth_time resolution and unequal Chaldean planetary hours"New value: +"Optional IANA timezone name (e.g. 'Europe/Madrid', 'Asia/Tokyo') to convert local `birth_time` to UTC and compute unequal Chaldean planetary hours."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, but the description goes further: zero-auth, stateless, no PII stored, and a clear split between the deterministic `soul_a` payload and the day-dependent `today_living_sky` transits. It also specifies the error contract ('invalid ISO dates return a structured JSON error'), which no structured field covers.

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?

Purpose and sibling routing are front-loaded, and the sentence order moves from what it produces, to when to use it, to guarantees, to parameter fallbacks. The eight-tradition enumeration is long but scopes the output surface for a highly niche tool; a small amount of density is the only cost.

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?

For a complex multi-system computation with six parameters and an output schema, the description covers the missing pieces: auth model, statefulness, determinism versus time-varying output, all optional-parameter fallbacks, and error behavior. Return-value detail is legitimately delegated to the output schema.

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 already 100%, so the baseline is 3, but the description adds consequence-level meaning the schema does not: omitting `birth_time` falls back to 12:00 UTC solar noon, supplying `tz` converts local time to UTC (affecting unequal Chaldean hours), and omitting `lat`/`lon` drops Placidus houses and the Ascendant. That tells an agent what is lost by leaving optional fields out, not just what the fields are.

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 opens with a specific verb and resource set: 'Compute a single person's deterministic natal chart, VVK-XXXX-YYYY Cosmic Soul Key, and 7-Wisdoms profile', then enumerates the eight traditions covered and adds the `today_living_sky` transit output. It explicitly distinguishes itself from the sibling tools that handle two people (`calculate_3d_soul_synastry`) and 3-31 people (`calculate_family_constellation_matrix`).

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

Usage Guidelines5/5

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

It names the exact selection rule: this tool for one individual, the synastry tool for two people, the constellation matrix for groups of 3 to 31. Prerequisite-free usage is also stated ('Zero-auth and stateless'), so an agent knows no setup call is needed before invoking it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.