Skip to main content
Glama

Cosmic Chemistry

Birth chart compatibility (Vedic synastry)

birth_chart_compatibility
Read-onlyIdempotent

Use this when someone asks whether two people are compatible in Vedic astrology, for synastry, or to compare two birth charts ("are we compatible", "compare my chart with my partner’s", "Vedic compatibility for me and my husband"). Returns each person’s Moon, Venus and Mars signs (and rising sign with a time), how the two Moon signs sit to each other, where each person’s Sun, Moon, Mars and Venus land in the other’s houses, and the strongest links between their planets. It gives no score and no verdict, and it is not the 36-point guna milan of kundli matching: say so if asked for gunas. Needs both dates and towns of birth; times make it exact. The first person is usually the one asking.

Input Schema

NameRequiredDescriptionDefault
person_a_birth_dateYesThe first person’s date of birth, YYYY-MM-DD.
person_a_birth_timeNoThe first person’s local clock time of birth, 24-hour HH:MM, if known.
person_b_birth_dateYesThe second person’s date of birth, YYYY-MM-DD.
person_b_birth_timeNoThe second person’s local clock time of birth, 24-hour HH:MM, if known.
person_a_birth_placeYesThe first person’s town or city of birth, with region or country if known.
person_b_birth_placeYesThe second person’s town or city of birth, with region or country if known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds valuable behavioral context: it returns no score or verdict, and specifies the exact astrological data returned. It doesn't cover error handling or rate limits, but those are minor for a read-only tool.

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 front-loaded with the primary use case and examples, then systematically covers output, limitations, and prerequisites. Every sentence serves a purpose; there is no redundant fluff.

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?

With no output schema, the description fully explains the return values and explicitly states what is not returned (score/verdict). It also covers input prerequisites and distinguishes from guna milan, making it complete enough for an agent given the annotations and 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 description coverage is 100%, so the baseline is 3. The description adds meaning by noting that times are optional but make results exact, and that the first person is usually the asker, clarifying the ordering of the two person parameters.

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 states a specific verb (compare/assess compatibility) and resource (two birth charts in Vedic astrology), and explicitly names what it returns. It distinguishes itself from the 36-point guna milan, which helps separate it from sibling tools like manglik_check or vedic_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 Guidelines5/5

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

It provides explicit when-to-use triggers (compatibility, synastry, comparing charts) with example queries, and a clear when-not: it is not for guna milan and should not be used for gunas. It also states prerequisites (both dates and towns needed; times optional).

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.

Resources