Skip to main content
Glama
cryptonaidu

VedIntel AstroAPI MCP

by cryptonaidu

get_kundali_match

Compute 36-point Guna Milan compatibility score between two birth charts across eight Ashtakoot categories. Input birth details for both individuals to assess Varna, Vashya, Tara, Yoni, Maitri, Gana, Bhakoot, and Nadi for matrimonial matching.

Instructions

Perform Kundali matching (Guna Milan / Ashtakoot) for two birth charts. Returns the 36-point compatibility score across 8 categories: Varna, Vashya, Tara, Yoni, Maitri, Gana, Bhakoot, and Nadi. Essential for matrimonial compatibility analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
m_dobYesMale date of birth DD/MM/YYYY
m_tobYesMale time of birth HH:MM
m_latYesMale birth place latitude
m_lonYesMale birth place longitude
m_tzYesMale birth place timezone offset
f_dobYesFemale date of birth DD/MM/YYYY
f_tobYesFemale time of birth HH:MM
f_latYesFemale birth place latitude
f_lonYesFemale birth place longitude
f_tzYesFemale birth place timezone offset
Behavior4/5

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

With no annotations provided, the description discloses the key behavioral trait: it returns a 36-point compatibility score across 8 categories. This is sufficient for a read-only analysis tool, though it could mention that inputs require accurate birth data.

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?

Description is concise (two sentences) and front-loaded with the main purpose. It efficiently communicates the core function and output without redundancy.

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?

Given the tool has 10 required parameters, no output schema, and no annotations, the description adequately explains what the tool does and what it returns. It could mention if the score is returned as a number or object.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema provides 100% parameter description coverage (10 parameters, all described). The description adds no parameter-specific information beyond what's in the schema, so baseline 3 is appropriate.

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 clearly states the tool performs Kundali matching (Guna Milan/Ashtakoot) for two birth charts, returns a 36-point compatibility score across 8 categories, and is essential for matrimonial compatibility analysis. The verb 'Perform' and specific resource 'Kundali matching' make the purpose unambiguous.

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?

The description indicates the tool is for matrimonial compatibility analysis, but does not explicitly state when not to use it or compare to siblings. Sibling tools like check_mangal_dosha or check_kaalsarp_dosha are related but distinct; no guidance on choosing between them.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cryptonaidu/vedintel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server