Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_ashtakoot

Computes Ashtakoot compatibility scores between a male and female from their birth date, time, and coordinates to support Vedic marriage matching.

Instructions

Execute ashtaKoot AstroChalit API

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": {
      "m_day": "<m_day>",
      "m_month": "<m_month>",
      "m_year": "<m_year>",
      "m_hour": "<m_hour>",
      "m_min": "<m_min>",
      "m_lat": "<m_lat>",
      "m_lon": "<m_lon>",
      "f_day": "<f_day>",
      "f_month": "<f_month>",
      "f_year": "<f_year>",
      "f_hour": "<f_hour>",
      "f_min": "<f_min>",
      "f_lat": "<f_lat>",
      "f_lon": "<f_lon>"
    },
    "name": "get_ashtakoot"
  }
}

Input Schema

NameRequiredDescriptionDefault
f_dayYesFemale Day of birth
f_latYesFemale Latitude
f_lonYesFemale Longitude
f_minYesFemale Minute of birth
m_dayYesMale Day of birth
m_latYesMale Latitude
m_lonYesMale Longitude
m_minYesMale Minute of birth
f_hourYesFemale Hour of birth
f_yearYesFemale Year of birth
m_hourYesMale Hour of birth
m_yearYesMale Year of birth
f_monthYesFemale Month of birth
m_monthYesMale Month of birth

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden but reveals almost nothing. It does not say whether the call is read-only, whether it returns a scored compatibility result, what units or koota breakdown to expect, or whether any of the 14 required inputs can be derived.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but it is under-specified rather than concise, and it front-loads an implementation reference ("AstroChalit API") instead of the purpose. There is nothing for an agent to act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A tool with 14 required parameters, no annotations, and no output schema needs real explanatory text, and this description supplies none. An agent cannot tell what the tool returns or how its inputs are meant to be conjointly provided.

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?

Schema description coverage is 100%, with every parameter labeled as male or female day/month/year/hour/minute/latitude/longitude, so the schema does the explanatory work. The description adds no additional meaning, but the documented baseline of 3 applies when the schema is this complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Execute ashtaKoot AstroChalit API" mostly restates the endpoint name and vendor API rather than stating what the tool does. It never says this computes Ashtakoota (eight-fold) marriage compatibility from two sets of birth data, and gives no basis for distinguishing it from siblings like get_dashakoot or get_compatibility_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite statement (e.g., both partners' full birth details are required), and no routing toward or away from the closely related compatibility siblings. An agent has to guess which matching tool to pick.

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

Deploy Server

Other Tools