Skip to main content
Glama

Supastro

Get the Choghadiya and Hora for a day

get_choghadiya
Read-onlyIdempotent

Calculates the Choghadiya of a day in a city: the eight day periods from sunrise and the eight night periods from sunset, each with its name, start and end time and what it is traditionally used for, plus the 24 planetary horas. Use it when someone asks for today's Choghadiya, the current Choghadiya or Hora, or the good time slots of a day. Times are in the city's own time zone. Covers today by default, or another date.

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional. The day as YYYY-MM-DD. Defaults to today in that city. Convert the person's own wording to this form; if an all-number date could be read two ways, ask which number is the day.
placeYesCity and country, for example "Ahmedabad, India".
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful domain context: the calculation covers day and night periods, the output includes names, start/end times and traditional uses, and times are given in the city's time zone with today as the default.

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 description is front-loaded with what is calculated and then gives usage conditions, with no wasted sentences. The final sentence about defaulting to today is slightly redundant with the date parameter's schema description, which keeps it from a 5.

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 read-only tool with no output schema, the description supplies the key return contents: period names, start and end times, traditional uses, and 24 planetary horas. It also covers time-zone handling and the default date, which is enough for an agent to invoke and interpret the tool correctly.

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 the place, date, latitude, and longitude parameters are already fully documented in the input schema. The description reinforces the default date and city time zone but adds little parameter-level meaning beyond what the schema already provides.

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 states a specific verb, 'Calculates', and a specific resource, Choghadiya, plus scope details: eight day periods, eight night periods, their names, times, traditional uses, and 24 planetary horas. It is clear what the tool returns, though it does not explicitly contrast itself with a sibling such as find_muhurat.

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 trigger conditions: today's Choghadiya, the current Choghadiya or Hora, or the good time slots of a day. It does not say when not to use it or name an alternative tool, so it falls short of full when/when-not guidance.

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