Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_compatibility_check

Evaluate relationship compatibility between a male and female zodiac sign by submitting both signs for Vedic astrology matchmaking analysis.

Instructions

Execute compatibility_check 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": {
      "maleSign": "<maleSign>",
      "femaleSign": "<femaleSign>"
    },
    "name": "get_compatibility_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
maleSignYesZodiac sign of the male (e.g. Aries, Leo)
femaleSignYesZodiac sign of the female (e.g. Aries, Leo)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing — not whether the call is read-only, what calculation is performed, whether it is deterministic, or what the response contains. "Execute ... API" is a wrapper statement, not behavioral context.

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 that is under-specification, not conciseness — every word is boilerplate that could apply to any tool in this server. There is no front-loaded statement of purpose or return value to anchor an agent.

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?

With no annotations, no output schema, and two required enum parameters, the description must explain what the tool returns and how to interpret a compatibility result. It supplies none of that, leaving the agent unable to judge output format or fitness relative to sibling match tools.

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% and both parameters have enums with per-field descriptions, so the schema fully documents maleSign and femaleSign. The description adds no additional meaning about these parameters, but the baseline of 3 applies when the schema does the heavy lifting.

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 compatibility_check AstroChalit API" only restates the tool name and names a provider; it never says what a compatibility check computes (romantic compatibility? astrological match score?) or what output the agent should expect. It does no work to distinguish this from siblings like get_ashtakoot or get_dashakoot, which are also relationship/score tools.

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?

No when-to-use guidance, no prerequisites, no exclusions, and no pointer to alternatives. An agent must guess whether this is the right tool versus the many other matching/score siblings; the definition offers no routing signal at all.

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