Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Marriage compatibility: the full reading

get_compatibility
Read-onlyIdempotent

Use this when the user asks whether two people are a good match for marriage and wants the full reading, not only a score. For the fast 36-point score with Manglik alone, use get_guna_milan. Both charts read together for marriage. The 36-point Aṣṭakūṭa (guna milan) is one input: the verdict names the governing factor and says when it outweighs the score. Also returned: each chart's marital promise, sustainability and happiness, progeny, Manglik reckoned from the lagna, the Moon and Venus with mutual cancellation, a joint marriage-timing window, synastry, and caveats where an uncertain birth time would change the reading. Deterministic: no language model is called. Each partner is a BirthData object plus optional name and gender. Cost: 12 credits per call (only successful calls are charged; a sandbox key is free and returns a fixed sample). Deterministic: the same input always gives the same answer. Example arguments: {"a":{"date":"1990-05-12","time":"14:35","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209,"name":"A"},"b":{"date":"1991-11-03","time":"06:10","timezone":"Asia/Kolkata","latitude":19.076,"longitude":72.8777,"name":"B"}}

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "get_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst partner: birth data plus optional name and gender.
bYesSecond partner: birth data plus optional name and gender.
referenceDateIsoNoISO date the reading is anchored to. Defaults to now.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / a / type
      Added value: +"object"
    • addedInput schema / properties / b / type
      Added value: +"object"
  2. Changed1 schema field changed
    • changedOutput schema / $defs / CorpusResolution / description
      Previous value: -"The weighed position of the classical corpus on this chart, as counts. Never source names on this surface."New value: +"How the classical evidence on this chart leans, as counts. Never source names on this surface."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, but the description adds substantial context: deterministic output, no language model, 12-credit cost, successful-call-only charging, free sandbox behavior, and caveats for uncertain birth time. It also lists the reading's components, including the verdict, marital promise, Manglik reckoning, timing window, synastry, and caveats.

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

Conciseness4/5

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

The description is front-loaded with the selection rule and alternative, then lists outputs, cost, determinism, and an example. It is somewhat long and repeats determinism twice, but most sentences carry useful information for an agent deciding whether and how to call the tool.

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

Completeness5/5

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

Given the rich annotations, full schema coverage, and an output schema, the description is complete enough for correct invocation. It covers selection, alternatives, output scope, cost, determinism, and birth-time caveats without needing to restate return-value structure.

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 the schema already documents the BirthData fields, optional name/gender, and referenceDateIso. The description adds a useful example and clarifies that each partner is a BirthData object plus optional name and gender, but it does not add much semantic detail beyond the schema, especially for referenceDateIso.

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

Purpose5/5

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

The description states a specific verb and resource: a full marriage-compatibility reading for two people. It explicitly distinguishes itself from get_guna_milan, the fast 36-point score, so an agent can select it without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use condition: the user asks whether two people are a good marriage match and wants the full reading, not only a score. It also names the alternative get_guna_milan for the fast 36-point score with Manglik alone.

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.