Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_get_chaugadiya_muhurta

Calculates Chaugadiya Muhurta time periods for a specified date and location using latitude and longitude, helping identify auspicious daily time windows.

Instructions

Execute get_chaugadiya_muhurta AstroChalit API

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": "get_get_chaugadiya_muhurta"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format (e.g. 2026-11-04)
latitudeYesLatitude of the location
longitudeYesLongitude of the location

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided and the description says nothing about behavior — whether the call is read-only, what the response contains (time windows, auspicious/inauspicious segments), or whether results depend on timezone. The full burden sits on the description and it carries none of it.

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

Conciseness2/5

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

It is a single short sentence with no wasted words, but it is under-specified rather than concise — the brevity comes from omitting purpose, not from tight writing.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only place an agent can learn what a Chaugadiya Muhurta result looks like or how to interpret it, and it supplies none of that. Domain terms like "Chaugadiya" are left undefined.

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%, with date format and latitude/longitude ranges fully documented in the schema, so the baseline of 3 applies. The description adds no parameter meaning beyond the schema, but is not required to.

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

Purpose2/5

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

The description restates the tool name ("Execute get_chaugadiya_muhurta AstroChalit API") rather than explaining what a Chaugadiya Muhurta is or what the tool returns. It names a resource but adds no distinguishing substance versus the sibling get_get_hora_muhurta, which is presumably a different muhurta calculation.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of prerequisites, and no differentiation from the muhurta-adjacent siblings. The agent gets nothing to decide between this and get_get_hora_muhurta.

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

Deploy Server

Other Tools