Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_dashakoot

Calculate Dasha Koot compatibility scores from a male and female birth date, time, and location for Vedic astrology matchmaking.

Instructions

Execute dashaKoot 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_dashakoot"
  }
}

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?

No annotations are supplied, so the description carries the full burden of behavioral disclosure and delivers almost nothing. 'Execute ... API' weakly implies a read-only remote computation, but the description never says whether it mutates state, what the response contains, or what errors may occur with 14 birth-detail parameters.

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?

Five words is not concision here, it is under-specification: the single sentence is front-loaded but carries no usable content. Nothing in it earns its place beyond echoing the name.

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 14-required-parameter tool with no annotations and no output schema needs the description to explain the computation, the meaning of dashaKoot, and what returning values represent. The description does none of this, leaving an agent unable to judge suitability or interpret results.

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 one of the 14 male/female birth date, time, and coordinate fields documented inline. The description adds no meaning beyond that baseline, which is acceptable but not additive.

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?

The description restates the tool name in different words: 'Execute dashaKoot AstroChalit API' says a dashaKoot-related call happens but never states what it computes, what dashaKoot means, or what the caller gets back. It distinguishes the tool from siblings like get_ashtakoot only by the jargon token in the name, not through any explanatory content.

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 guidance on when to call this versus get_ashtakoot or get_compatibility_check, no prerequisites, and no stated exclusions. The only hint is the word 'dashaKoot' itself, which an agent cannot act on without prior domain knowledge.

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