Skip to main content
Glama
socraticsurge

mcp-server-panchangam

find_muhurta

Find ranked auspicious time slots for any activity, filtered by panchangam factors like Rahu Kalam, Varjyam, and tarabalam. Supports travel, ceremonies, and more with customizable birth star and rashi scoring.

Instructions

Find ranked auspicious time slots over the coming days. Slots are good choghadiya blocks (Amrit/Shubh/Labh/Char) with every inauspicious window subtracted (Rahu Kalam, Gulika, Yamagandam, Varjyam, Durmuhurtham), scored with Abhijit Muhurta / Amrita Kalam overlap and special-yoga bonuses. activity tunes the rules: travel additionally avoids Vishti karana, ceremony skips Visha/Dagdha days, purchase favours Labh, beginning favours Amrit. New in 1.9.0: Bhadra Mukha is a hard-avoid cut; Bhadra Puchha is a bonus for litigation; Simha-Stha Guru/Shukra, Guru/Shukra Maudhya (combustion), Khar-Maasa, Adhika Maasa, and Pitru Paksha are all skipped for samskara activities; Panchaka Rahita (Mrityu/Agni/Raja/Chora/Roga) is checked at both day-level (sunrise lagna) and slot-level; optional travel_direction parameter activates Disha Shoola filtering. New activities: litigation, cremation, construction_roof, wood_cutting, well_digging, coronation. Pass janma_nakshatras (1-4 birth stars) to keep only days whose tarabalam favours everyone. Optionally pass janma_rasis (aligned with janma_nakshatras, null entries allowed) to add Chandrabalam scoring — each person then gets the Moon's position from their rashi with a verdict (good / needs remedial puja / avoid), and chandra_mode selects how this affects the day filter: 'stars' (annotate only, default), 'puja_ok' (drop Moon-avoid days), 'strict' (Moon must be good). Optionally pass janma_lagnas (aligned, null entries allowed) to use strict Lagna Shuddhi for that person — kendra/trikona/Ashtama count from the natal ascendant; otherwise we fall back to counting from janma_rasis (Chandra-Rashi-as-lagna tradition). include_night=True adds night choghadiya slots (sunset to next sunrise) scored by the same panchangam factors but without Rahu Kalam / Gulika / Yamagandam / Abhijit, and with Brahma Muhurta (+2) and Nishita Kala (+2) as night bonuses. Args: start_date=YYYY-MM-DD, days=1-14, activity=any|travel|purchase|ceremony|beginning|litigation|cremation|construction_roof|wood_cutting|well_digging|coronation, city=city name (or latitude+longitude), system=drik|surya_siddhanta|vakya, janma_rasis=optional birth rashis (e.g. ['Meena', 'Simha']), janma_lagnas=optional birth lagnas (e.g. ['Vrishabha', None]), chandra_mode=stars|puja_ok|strict, ayanamsa=lahiri|raman|krishnamurti|true_chitrapaksha (default: lahiri), travel_direction=optional compass direction (N/S/E/W/NE/NW/SE/SW) to activate Disha Shoola filtering for travel activity, include_night=false|true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoHyderabad
daysNo
systemNodrik
activityNoany
ayanamsaNolahiri
latitudeNo
timezoneNo
longitudeNo
start_dateYes
janma_rasisNo
chandra_modeNostars
janma_lagnasNo
include_nightNo
janma_nakshatrasNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It details scoring, activity tuning, new features, and constraints (e.g., Bhadra Mukha hard-avoid, Disha Shoola filtering). No contradictions.

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 long but efficient, front-loading the main purpose. It could be more structured (e.g., bullet points), but every sentence adds value, covering many details without redundancy.

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?

Given 14 parameters and an output schema, the description covers nearly all aspects, including return value indications (scored slots). It omits explicit output schema details but provides sufficient context for agent decision-making.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must explain all parameters. It does so thoroughly, describing each parameter's purpose, default values, and examples (e.g., janma_rasis format, chandra_mode options).

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 clearly states the tool finds ranked auspicious time slots over coming days, with specific criteria. It distinguishes itself from siblings like get_muhurta and find_tarabalam_days by detailing the computation and activity-specific tuning.

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?

The description provides extensive context on when to use the tool, including activities, optional parameters like janma_nakshatras, and modes. It lacks explicit contrast with sibling tools but covers many usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/socraticsurge/telugu-calendar-utilities'

If you have feedback or need assistance with the MCP directory API, please join our Discord server