Homo Universalis — Viveka Oracle

calculate_3d_soul_synastry

Read-onlyIdempotent

Compare two ISO YYYY-MM-DD birth dates to compute deterministic 3D astrological and 7-Wisdoms compatibility, including symmetric scores and directional soul gift roles.

Instructions

Compute deterministic 3D astrological and 7-Wisdoms compatibility between two ISO YYYY-MM-DD birth dates (birth_date_a and birth_date_b). Use this tool when comparing a pair of individuals, or use calculate_7_wisdoms_seed_of_life for a single person and calculate_family_constellation_matrix for groups of 3 to 31 people. Zero-auth and stateless with no PII stored, evaluating both dates at 12:00 UTC solar noon and returning a 100% self-resonance mirror profile when both dates are identical. Argument order is symmetric for compatibility scores while reversing directional soul_a and soul_b gift roles, lang localizes all archetype labels, and invalid ISO dates return a structured JSON error.

Input Schema

Name	Required	Description	Default
`lang`	No	Output language for localized synastry archetypes and narrative ('es' Spanish, 'en' English, or 'ca' Catalan).	es
`birth_date_a`	Yes	First person's ISO birth date in YYYY-MM-DD format (e.g. '2000-03-20').
`birth_date_b`	Yes	Second person's ISO birth date in YYYY-MM-DD format (e.g. '1985-11-12').

Output Schema

Name	Required	Description	Default
`soul_a`	Yes
`soul_b`	Yes
`three_dimensional_resonance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive behavior, and the description adds genuinely new traits: zero-auth, stateless, no PII stored, evaluation at 12:00 UTC solar noon, a self-resonance mirror profile for identical dates, and structured JSON errors on invalid ISO input.

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?

Front-loads the purpose and packs scope, alternatives, and behavioral traits without filler. It is dense as a single long sentence with several parenthetical clauses, which slightly taxes scanning but every clause carries 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?

An output schema exists so return values need no explanation, and the description still covers input format, symmetry semantics, localization, edge case of identical dates, and error behavior. Nothing an agent needs to call this correctly is missing.

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%, so the baseline is 3, but the description adds real semantic meaning: argument order is symmetric for compatibility scores yet reverses the directional soul_a and soul_b gift roles, and lang localizes all archetype labels. That is behavior the schema alone does not convey.

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?

States a specific verb and resource: 'Compute deterministic 3D astrological and 7-Wisdoms compatibility between two ISO birth dates'. It immediately distinguishes itself from the sibling tools by scoping to a pair rather than a single person or a group.

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?

Explicitly says 'Use this tool when comparing a pair of individuals' and names the alternatives with their conditions: calculate_7_wisdoms_seed_of_life for one person and calculate_family_constellation_matrix for groups of 3 to 31. The routing decision is fully resolved.

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

Deploy Server