Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_tithi

Read-onlyIdempotent

Retrieve tithi (lunar day) details for a given date and location, including current tithi, paksha, start/end times, and deity.

Instructions

Get tithi (lunar day) details for a given date and location.

Returns the current tithi, paksha (Shukla/Krishna), start/end times, and deity.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results are computed for a specific date and location (astronomical computation, so results vary by place/timezone), which is useful context, but it does not mention rate limits, upstream validation failures, or that invalid place/date combos error out.

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 tight sentences with no filler and the core purpose front-loaded. The word "current" in the return sentence is slightly at odds with a date-parameterized query, but this is a minor imprecision rather than bloat.

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

Completeness3/5

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

An output schema exists, so enumerating return fields is not strictly required, and the description does anyway. However, for a tool whose every parameter is required, failing to mention timezone and coordinates leaves the agent underprepared; the definition is adequate but not complete.

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?

Coverage is reported at 0% for the single top-level `params` object, so the description must compensate, and it only mentions "date and location". It omits the required timezone offset, the latitude/longitude requirement, and the non-ISO language code quirk (e.g. 'ma' for Marathi, 'tm' for Tamil), all of which are the parameters most likely to be mis-set.

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 gives a specific verb and resource ("Get tithi (lunar day) details") and scopes it to "a given date and location", which is enough to distinguish it from the sibling list-style tool divine_get_month_tithi_list. It stops short of explicitly naming or contrasting that sibling, so it is clear but not differentiating.

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 when-to-use or when-not-to-use guidance, and no alternative is named despite many panchang-related siblings (month tithi list, auspicious timings, choghadiya). The only implied usage is "single date lookup", which the agent must infer.

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