Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_manglik_report

Generate a Manglik (Mangal Dosha) compatibility report from male and female birth details. Assess dosha presence and matchmaking implications.

Instructions

Execute manglik_report 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_manglik_report"
  }
}

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.3/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 behavioral burden, yet it says nothing about whether the call is read-only, whether it computes or stores anything, what the response contains, or how errors are surfaced. The word "Execute" vaguely implies a computation over supplied inputs, but nothing about side effects or output is disclosed.

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

Conciseness3/5

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

It is one short, front-loaded sentence with no padding, so nothing is wasted. However, the brevity comes from omission rather than efficiency, leaving the definition under-specified for a 14-parameter tool.

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

Completeness2/5

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

For a tool with 14 required parameters, no annotations, and no output schema, the description supplies none of the context an agent needs: no statement of what a manglik report is, no distinction from get_manglik_dosha_report, and no note on what the response looks like. The fully described schema is the only reason this is callable at all.

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%, so all 14 required male/female birth date-time and coordinate parameters are already documented in the schema. The description adds no meaning beyond that (e.g., why both sets of birth data are needed, or expected coordinate format), so the baseline 3 applies.

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 manglik_report AstroChalit API" names a resource but the verb is just "Execute ... API", which restates the fact that a tool call happens rather than describing what the tool produces. It also fails to distinguish it from the near-identical sibling get_manglik_dosha_report, so an agent cannot tell which of the two manglik tools to pick.

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 at all: no mention of prerequisites (both partners' birth data), no exclusions, and no reference to the overlapping get_manglik_dosha_report sibling. The only usable signal is the name itself.

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