Skip to main content
Glama

AstroLogics

Marriage compatibility (36 guna)

check_marriage_compatibility
Read-onlyIdempotent

Calculate the 36-guna Ashtakoota marriage compatibility score between two people from their birth details. The calculation is Moon-based, so birth time is optional; supplying it is more accurate because the Moon moves about 13 degrees a day.

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": {
      "boy": "<boy>",
      "girl": "<girl>"
    },
    "name": "check_marriage_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
boyYesFirst person: birth date, optional time, latitude and longitude.
girlYesSecond person: birth date, optional time, latitude and longitude.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.",
      +  "enum": [
      +    "en",
      +    "hi"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, closed-world, non-destructive call, so the safety profile is covered. The description adds genuine domain behavior beyond that: the calculation is Moon-based and time is optional but improves accuracy because the Moon moves ~13 degrees a day. It does not describe the result at all (score out of 36, koota breakdown, interpretation), which matters since there is no output schema.

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

Conciseness5/5

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

Two sentences, front-loaded with the verb and resource, followed by the single most consequential caveat. No filler, no restatement of the title, nothing that could be cut without losing information.

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

Completeness3/5

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

The tool has nested input objects and no output schema, which puts the burden on the description to say what comes back. It explains the inputs and the calculation basis adequately but never states the shape of the result (overall score out of 36, per-koota breakdown, verdict), so an agent cannot prepare the user for the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description earns above that by explaining the one non-obvious parameter decision: 'time' is not required but supplying it is more accurate, with a stated reason. It says nothing extra about the boy/girl nested objects or the language enum, but those are already documented in the schema.

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

Purpose4/5

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

The description gives a specific verb and resource: 'Calculate the 36-guna Ashtakoota marriage compatibility score between two people from their birth details.' It is unambiguous what is computed and from what inputs, and it is naturally distinct from the dosha-check siblings. It stops short of explicitly contrasting itself with any sibling, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

Usage is implied by the stated purpose (matchmaking compatibility between two people), and the description does add a useful conditional around birth time. But there is no explicit 'use this when…' framing or routing to alternatives such as the dosha-check tools that an agent might also consider for a marriage question.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources