Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_match_birthchart

Generate a match birth chart by submitting birth date, time, and coordinates for both male and female, returning compatibility-focused astrological chart data.

Instructions

Execute match_birthChart 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_match_birthchart"
  }
}

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

D1.7/5.0
Behavior1/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, yet it discloses nothing about behavior: no output shape, no accuracy or ephemeris caveats, no timezone or coordinate convention, no rate limits. The only behavioral signal is the word 'Execute', which tells the agent nothing actionable.

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?

One short phrase, so nothing is padded, but it is under-specified rather than concise. The visible typo 'AstroChalit' and the camel-case API name leak internal naming rather than describing capability.

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?

For a tool requiring 14 mandatory parameters, with no annotations and no output schema, the description should explain what a 'match birth chart' produces (e.g., compatibility score, chart comparison) and how the two people's data are consumed. Essentially none of that is present, leaving the agent unable to judge whether calling it is appropriate.

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 every one of the 14 parameters is already documented as male/female day, month, year, hour, minute, latitude, and longitude. The description adds no meaning beyond that; baseline 3 applies because the schema does all the work.

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 is essentially the tool name restated as a sentence: 'Execute match_birthChart AstroChalit API'. It hints at a male/female birth-chart matching operation, but it never says what is actually returned or how it differs from siblings such as get_compatibility_check, get_ashtakoot, or get_dashakoot. An agent cannot distinguish the matching semantics from the name alone.

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

Usage Guidelines1/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 prerequisites, and no mention of any alternative tool. Given at least three sibling compatibility/matching tools exist, the absence of any routing guidance is a serious gap.

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