Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_karana

Read-onlyIdempotent

Retrieve karana (half-tithi) details for a date and location to identify auspicious timing for Vedic astrology activities.

Instructions

Get karana details for a given date and location.

Karana is half of a tithi. There are 11 karanas in Vedic astrology, each with specific qualities for timing 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_karana"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description contributes domain context (what a karana is) but says nothing about result shape, timezone sensitivity, or how many karanas come back for a given date — gaps partly mitigated by the existing output schema.

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, front-loaded with the action and followed by the minimal domain definition needed to interpret 'karana'. Little waste, though the trailing explanatory sentence is purely glossary material.

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?

For a read-only single-object query with a rich nested schema, full annotations, and an output schema, the description covers what the tool returns conceptually. The main missing piece is disambiguation from the crowded set of sibling panchang tools.

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?

The description only echoes that a date and location are needed; it adds nothing about the timezone, language code, or coordinate format that the nested PanchangInput schema already documents field by field. With schema documentation doing the work, baseline 3 applies.

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 karana details') plus the scoping inputs ('for a given date and location'), and defines the domain concept (half a tithi, 11 karanas). It does not distinguish itself from sibling panchang tools such as divine_get_choghadiya or divine_get_auspicious_timings, which also return timing segments.

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 via 'specific qualities for timing activities', which hints at activity timing but never states when to pick this tool over the many other panchang/timing siblings. No exclusions, prerequisites, or alternative routing are given.

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