Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_get_hora_muhurta

Retrieves Hora and Muhurta timings for a given date and geographic coordinates, helping users identify auspicious periods for Vedic astrology planning.

Instructions

Execute get_hora_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_hora_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

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It indicates that an external AstroChalit API is executed, but does not clarify whether the operation is read-only, what kind of result is returned, or any authentication, rate-limit, or failure considerations.

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

Conciseness3/5

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

The single short sentence is direct and contains no repetitive wording. However, its brevity primarily reflects missing substance rather than efficient communication of useful selection or invocation details.

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?

The schema is sufficient to supply the three required inputs, but the definition does not explain the domain purpose or expected result. With no annotations and no output schema, the absence of behavioral and result context leaves substantial gaps despite the tool's simple parameter structure.

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%: the date format and both coordinate inputs are documented, with numeric bounds for latitude and longitude. The description adds no parameter meaning beyond that schema, so the high-coverage baseline of 3 applies.

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 mostly restates the tool name as "Execute get_hora_muhurta AstroChalit API," adding only the API provider. It does not explain what a hora muhurta calculation produces or distinguish it from siblings such as get_get_chaugadiya_muhurta.

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

Usage Guidelines2/5

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

There is no guidance about when an agent should request this calculation, what user need it serves, or when another muhurta or astrology tool would be more appropriate. Usage must be inferred almost entirely from the opaque tool name.

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