Skip to main content
Glama

AstroLogics

Gand Mool nakshatra check

check_gand_mool
Read-onlyIdempotent

Check whether a person was born with the Moon in a Gand Mool nakshatra (Ashwini, Ashlesha, Magha, Jyeshtha, Mula or Revati), with the pada and whether it falls on the sign junction (gandanta). Birth time is optional; without it the result says if the Moon changed nakshatra that 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": {
      "date": "<date>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "check_gand_mool"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
timeNoLocal birth time, HH:MM. Optional.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
latitudeYesBirth latitude in decimal degrees.
longitudeYesBirth longitude in decimal degrees.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. Beyond that, the description discloses the shape of the answer (pada and whether it lands on the sign junction / gandanta) and the fallback behavior for missing time, which is genuine added context. It does not discuss precision limits of the calculation, which keeps it out of 5 territory.

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?

A single front-loaded sentence delivers the check, the nakshatra list, the outputs, and the optional-time caveat with no filler. The parenthetical enumeration is information-dense rather than redundant.

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

Completeness4/5

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

For a read-only, closed-world calculation tool with no output schema, the description covers purpose, inputs, degradation path, and the key result fields. A little more on the exact response shape or the significance of a positive result would make it fully self-sufficient, but nothing essential is missing.

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 the baseline is 3, and the description adds real meaning for the optional `time` parameter by explaining what the result degrades to without it. It says nothing about the `language` enum or the latitude/longitude meaning, but the schema documents those adequately, so the small lift above baseline is warranted.

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?

States a specific verb and resource ("Check whether a person was born with the Moon in a Gand Mool nakshatra") and enumerates the six relevant nakshatras plus the pada/gandanta determinations returned. That precision separates it cleanly from sibling dosha checks like check_manglik_dosha or check_kaal_sarp_dosha without needing to name them.

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

Usage Guidelines4/5

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

Gives clear usage context by declaring birth time optional and spelling out the degraded-but-still-useful answer when it is omitted (whether the Moon changed nakshatra that day). It does not explicitly route to or exclude sibling tools, so it stops short of a 5, but an agent knows exactly when this call is appropriate.

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