Skip to main content
Glama

Supastro

Find auspicious times (muhurat)

find_muhurat
Read-onlyIdempotent

Finds auspicious date-and-time windows in the coming weeks for an activity in a city: a wedding or engagement, house-warming, business launch, travel, signing, buying property or a vehicle, a job start, starting studies, or a medical procedure. Each window is clear of Rahu Kaal, Yamaganda, Gulika, Varjyam, Dur Muhurtam and Bhadra, and is given with its star, tithi, Choghadiya and the reasons it qualifies. With birth details it also applies the person's Tara Bala and Chandra Bala. Use it when someone asks for a good date or time to do something. A wedding, house-warming or vehicle window also respects the season rules of the muhurat calendar.

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": {
      "activity": "<activity>",
      "place": "<place>"
    },
    "name": "find_muhurat"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoOptional. How many days ahead to search, 7 to 45. Defaults to 30.
placeYesCity and country where it will happen, for example "Pune, India".
activityYesWhat the time is for. Use general for anything else important.
latitudeNoOptional. Latitude of the city in decimal degrees, north positive. Give it only together with longitude, when the user supplied coordinates or the place could not be found by name.
longitudeNoOptional. Longitude of the city in decimal degrees, east positive. Give it only together with latitude.
birth_dateNoOptional. Date of birth as YYYY-MM-DD. Give it together with birth_time and birth_place to make the answer personal. People write dates in different orders: day first in India and most countries, month first in the United States. Convert what the person wrote to YYYY-MM-DD yourself. If an all-number date could be read two ways, such as 05-06-1990, ask which number is the day before calling; never assume.
birth_timeNoOptional. Local clock time of birth, 24-hour HH:MM. If the person gave an hour from 1 to 12 without AM or PM, ask which before calling. Ask the user if the time is unknown; do not guess it.
birth_placeNoOptional. City and country of birth, for example "Mumbai, India".
birth_latitudeNoOptional. Latitude of the birth place, north positive. Only together with birth_longitude.
birth_longitudeNoOptional. Longitude of the birth place, east positive. Only together with birth_latitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description explains that each window is clear of specific inauspicious periods and reports star, tithi, Choghadiya, and qualifying reasons. It also discloses personalization via birth details and season rules for certain activity types.

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 definition is front-loaded with purpose and systematically covers output, usage, personalization, and seasonal rules. It is dense but mostly earns its length, though the long activity list in the first sentence could be tightened.

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?

For a 10-parameter tool with no output schema, the description supplies the missing context: what a returned window includes and how birth details affect results. It is sufficiently complete for an agent to understand the tool’s domain behavior.

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 schema carries most parameter meaning. The description still adds useful semantics by explaining that birth details trigger Tara Bala and Chandra Bala, and that certain activity windows respect muhurat season rules.

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 uses a specific verb and resource: 'Finds auspicious date-and-time windows' for named activities in a city. It clearly scopes the tool with examples and distinguishes its output by listing the inauspicious periods it avoids.

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?

It gives explicit when-to-use guidance: 'Use it when someone asks for a good date or time to do something.' It does not name alternatives or state when not to use it, which keeps it from a 5.

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