Skip to main content
Glama

AstroLogics

Choghadiya for a day

get_choghadiya
Read-onlyIdempotent

Get the 16 day and night choghadiya periods for a date and place with their quality (auspicious or not), start and end times in local time, the period running now and the next favourable one.

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_choghadiya"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate, YYYY-MM-DD.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
latitudeYesLatitude in decimal degrees.
longitudeYesLongitude in 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

A3.7/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false already supplied, the description still adds real context: results are computed for a date and coordinates, times are expressed in local time, and the payload includes the currently running period plus the next favourable one. That last point also signals a dependence on server-side 'now' even though the call is idempotent, which is useful for an agent to know. It says nothing about boundary behavior (e.g. what happens outside the computed day) or error conditions for invalid coordinates.

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?

It is a single front-loaded sentence that leads with the verb and resource before listing return content, with no filler or repetition of the title. The trailing enumeration of outputs is dense but each clause carries information an agent needs given the absence of an output schema. Slightly heavy for one sentence, but not wasteful.

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?

There is no output schema, so the description must carry the return shape, and it does: period count, quality flags, start/end times in local time, the current period, and the next favourable one. All four parameters are documented in the schema and the read-only, closed-world nature is fully covered by annotations. The only residual gap is how 'place' and coordinate precision affect results, which is minor for a deterministic astronomical calculation.

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, latitude, longitude, and the en/hi language enum all documented in the schema itself, so the baseline is 3. The description only refers to 'a date and place' and does not mention the language option or the coordinate semantics, adding no meaning beyond the schema. It does not compensate for anything because compensation is not needed.

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?

The description names a specific verb and resource ('Get the 16 day and night choghadiya periods') and enumerates what comes back: quality, start/end times in local time, the current period, and the next favourable one. An agent can tell this is a per-day auspicious-timing lookup. It does not name a sibling such as find_muhurat or get_panchang to sharpen the boundary, so it stops short of a 5.

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?

Usage is only implied through the required date and place and the mention of the 'next favourable' period, so an agent can infer this is for choosing an auspicious window. There is no explicit when-to-use statement and no exclusion or routing against find_muhurat, get_panchang, or the dasha/chart siblings. Adequate but leaves the alternative-selection decision to inference.

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