Skip to main content
Glama

Supastro

Compare two birth charts for compatibility

compare_two_charts
Read-onlyIdempotent

Reads two birth charts together across eight layers: the two birth charts (D1), the Navamsa (D9), Jaimini factors (Upapada, A7, Darakaraka), Ashtakavarga, both Manglik checks with their cancellations, dasha timing, the chart-to-chart planet links, and the 36-point Ashtakoota table as one layer among them. It returns a score for each layer with the findings behind it, the overall score and verdict band, Nadi and Bhakoot dosha with any cancellation, and the periods in which both people's relationship planets are active together. Use it when someone asks about compatibility, kundli matching or gun milan between two people. Both people's birth date, time and place are needed.

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": {
      "person_a": "<person_a>",
      "person_b": "<person_b>"
    },
    "name": "compare_two_charts"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_aYes
person_bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the read-only, idempotent, non-destructive profile; the description goes far beyond by disclosing the return payload (per-layer score with underlying findings, overall score and verdict band, Nadi/Bhakoot dosha with cancellation, joint activation periods). With no output schema present, this is exactly the kind of disclosure that carries the burden.

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-loaded with purpose, then return values, then usage — a sensible order with no filler sentences. The opening sentence is dense with domain jargon and a long list, but every item named is a real output layer an agent may need to report, so the length is earned.

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?

For a complex nested-input tool with no output schema, the description covers what is returned, at what granularity, and what inputs are mandatory. The only remaining gap is operational context such as missing-time fallback behavior or latency, which an agent could otherwise want before calling.

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?

The top-level person_a/person_b properties carry no inline description (coverage reported as 0% at top level), so the description's statement that both people's birth date, time and place are required is genuinely useful. The deep nested fields (date-format ambiguity handling, optional gender, latitude/longitude pairing) are covered exhaustively inside the schema, so no further parameter detail is needed here.

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 ('reads two birth charts together') and enumerates exactly what is computed across the eight layers, so an agent can distinguish this two-chart comparison from single-chart siblings like get_divisional_charts or check_doshas without opening the schema.

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?

'Use it when someone asks about compatibility, kundli matching or gun milan between two people' gives a clear triggering condition, and the closing sentence states the data prerequisite (both people's date, time and place). It stops short of naming an alternative sibling or a when-not case, so it is strong but not the explicit routing seen in top-tier definitions.

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