Skip to main content

Dashakoot

asterwise_get_dashakoot

Computes the ten-koota Dashakoot grid for two charts, converts it to a ten-point score with percentage, and exposes boolean dosha flags plus supplementary diagnostics.

Parameters

ParameterTypeRequiredDescription
person1objectyesBirth data for a single person. Fields: date, time, lat, lon*, person_name, timezone, ayanamsa
person2objectyesBirth data for a single person. Fields: date, time, lat, lon*, person_name, timezone, ayanamsa
response_formatenum: markdown, jsonno

What it covers

South Indian Kannada/Telugu style matching: each koota scores 0.0 or 1.0 with max_per_koota 1.0, includes Nadi/Bhakoot/Rajju/Vedha blocks, Mahendra/Stree Deergha supplements, and Rajju/Vedha detail objects. It is not Ashtakoota 36-point (asterwise_get_compatibility) or Tamil porutham pass grid (asterwise_get_porutham).

Workflow

BEFORE: RECOMMENDED — asterwise_get_natal_chart for each native — context before regional scoring.
AFTER: asterwise_get_papasamyam — optional malefic differential.

Input

Two BirthData objects per global contract.

Output contract

data.total_score (float — out of 10)
data.max_score (float — 10.0)
data.percentage (float)
data.compatibility_level (string)
data.breakdown{} — keys Dina, Gana, Mahendra, StreeDeergha, Yoni, Rasi, RasiAdhipati, Vashya, Rajju, Vedha — each float 0.0 or 1.0
data.max_per_koota{} — each value 1.0
data.doshas{}:
nadi_dosha (bool)
nadi_cancelled (bool)
bhakoot_dosha (bool)
bhakoot_cancelled (bool)
rajju_dosha (bool)
rajju_group_boy (string or value per upstream)
rajju_group_girl (string or value per upstream)
vedha_dosha (bool)
vedha_pair (string or value per upstream)
data.supplementary:
mahendra (object)
stree_deergha (object)
rajju — { boy_rajju, girl_rajju, same_rajju (bool), is_dosha (bool), description (string) }
vedha — { has_vedha (bool), boy_nakshatra (int), girl_nakshatra (int), description (string) }
dina_inclusive_count (int)

Response format

response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode.

Compute class

MEDIUM_COMPUTE

Errors

INVALID_PARAMS (local — caught before upstream call):
None — all validation is upstream.

INVALID_PARAMS (upstream):
— None — upstream rejection surfaces as MCP INTERNAL_ERROR at the tool layer.

INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR

Edge cases:
— Read rajju/vedha supplementary objects before trusting the headline score.

Do not confuse with

asterwise_get_compatibility — North Indian 36-point Ashtakoota with different breakdown keys.
asterwise_get_porutham — Tamil ten-porutham passed counts, not Dashakoot floats.

Connect

Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.