Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_choghadiya

Read-onlyIdempotent

Retrieve auspicious time slots for a given date and location, splitting day and night into planetary periods that indicate favorable or unfavorable times for activities.

Instructions

Get Choghadiya (auspicious time slots) for a given date and location.

Divides the day and night into multiple slots, each ruled by a different planet, indicating good/bad periods for various activities.

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": {
      "params": "<params>"
    },
    "name": "divine_get_choghadiya"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered without description help. The description adds useful structural context (day and night split into planetary slots marking good/bad periods) that helps interpret output, but says nothing about required location/timezone precision, rate limits, or how ambiguous locations are resolved.

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 short sentences with the resource and scope front-loaded, no boilerplate or repetition. Slight loss because the second sentence describes the domain concept rather than operational detail an agent needs to invoke the tool.

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?

With an output schema present and rich annotations, the description need not explain return values, and it correctly focuses on what the tool produces. What remains missing is minimal: the fact that coordinates and a UTC-offset timezone are required inputs and that a response language can be selected.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Reported schema description coverage is 0%, so the description is expected to compensate for the nested 'params' object, yet it adds no detail about day/month/year format, latitude/longitude, timezone offset, or the language code. It only says 'given date and location', which is a weaker statement than the input requires and omits that timezone and coordinates are mandatory.

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 ('Get Choghadiya ... for a given date and location') and defines the domain concept as auspicious time slots ruled by planets. It is clear on its own, but does not distinguish itself from close siblings such as divine_get_auspicious_timings, divine_get_inauspicious_timings, or divine_get_gowri_panchangam, leaving overlap to inference.

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: the description explains what Choghadiya is and that it indicates good/bad periods, from which an agent can infer when to call it. There is no explicit when-to-use, when-not-to-use, or alternative-tool routing despite several sibling tools covering adjacent timing concepts.

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