Skip to main content
Glama

AstroLogics

Find auspicious dates (muhurat)

find_muhurat
Read-onlyIdempotent

Find the most auspicious upcoming dates for an activity using panchang rules (tithi, nakshatra, yoga, weekday, Panchak, Tara Bala). Activities: marriage, griha-pravesh, business, vehicle, travel, education, namkaran, property.

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>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "find_muhurat"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many dates to return. Defaults to 10.
daysNoHow many days to scan. Defaults to 90.
fromNoFirst date to consider, YYYY-MM-DD. Defaults to today.
activityYesThe activity to find dates for.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
latitudeYesLatitude of the place, decimal degrees.
longitudeYesLongitude of the place, decimal degrees.

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by revealing the derivation rule set, but says nothing about what a returned date contains (score, reasoning, per-rule breakdown) or how results behave when no auspicious date exists in the window — a meaningful gap given 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.

Conciseness4/5

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

Two tight sentences with the core purpose front-loaded and the rule set and activity list as supporting detail; nothing is padding. Minor redundancy in re-listing the activities that the enum already enumerates.

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?

A seven-parameter, computation-heavy tool with no output schema needs the description to convey the shape of the answer, and it does not — an agent cannot tell whether each result is a bare date, a date plus score, or a date plus reasoning. The purpose and rule basis are well covered, so this is adequate but with a clear gap.

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 every parameter including defaults (top=10, days=90, from=today) is already documented in the schema. The description's activity list mirrors the enum and adds no per-parameter meaning such as how 'days' interacts with 'top' or why latitude/longitude matter for panchang computation; baseline 3 applies.

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?

States a specific verb and resource ('find the most auspicious upcoming dates for an activity') and even discloses the underlying computation method (tithi, nakshatra, yoga, weekday, Panchak, Tara Bala), which makes the tool's intent unmistakable. It stops short of naming a sibling it is not (e.g., get_panchang for raw panchang data, get_choghadiya for time windows), so the differentiation is left implicit.

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?

The enumerated activity list strongly implies when to call it — a user asking 'when should I get married' — but there is no explicit when-to-use or when-not-to-use statement, and no routing toward get_panchang or get_choghadiya when the user wants raw panchang elements rather than a curated date recommendation.

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