Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_basic_astro_details

Read-onlyIdempotent

Retrieve basic Vedic astrological details like tithi, nakshatra, and rashi from birth data to generate a person's astrological profile.

Instructions

Get basic astrological details for a person based on their birth data.

Returns tithi, nakshatra, rashi, sun sign, moon sign, yoga, karana, varna, vashya, yoni, gana, nadi, ayanamsha, and more. vaar is the weekday of birth; with weekday='vedic' a birth before sunrise gets the previous day's vaar.

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

Input Schema

NameRequiredDescriptionDefault
paramsYesBirth details
weekdayNoHow the weekday (vaar) is counted: 'civil' (default) changes the day at midnight, like a calendar; 'vedic' changes it at local sunrise, so a moment between midnight and sunrise still belongs to the previous day (e.g. 04:30 on a Thursday is Wednesday). Only matters before sunrise.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the vaar edge case where a pre-sunrise birth under weekday='vedic' pulls the previous weekday, which is a subtle output-affecting rule the agent could not guess. It stops short of noting external-service dependency, latency, or error behavior, which is acceptable given openWorldHint and an 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?

The purpose is front-loaded in a single clear sentence, followed by the return-field list and then the conditional weekday rule, which is a sensible ordering. The enumerated output list ending in 'and more' is somewhat low-value padding, especially since an output schema exists, but the block is short enough not to impede scanning.

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 single-purpose read-only computation with a 100%-documented 2-parameter schema and an output schema, the description covers purpose and the one non-obvious behavioral rule. The remaining gap is disambiguation from sibling basic-astro tools, which matters here given the crowded sibling set.

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 baseline is 3; every birth field (day, month, hour, lat, lon, tzone, gender, lan) is already documented in the schema with examples. The description adds only the weekday='vedic' semantics, which the schema itself also explains in comparable detail, so the added meaning is marginal and largely restated.

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 basic astrological details for a person based on their birth data' — and enumerates the outputs (tithi, nakshatra, rashi, sun/moon sign, etc.), so the agent knows exactly what it produces. It does not, however, distinguish itself from near-identical siblings such as divine_get_varshphal_basic_astro_details or divine_get_matching_basic_astro, leaving selection between them 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 agent can infer this is the entry-level chart-detail call for a single person's birth data, and the weekday note clarifies a conditional ('Only matters before sunrise'). There is no explicit when-to-use statement, no prerequisite guidance (e.g. that ayanamsha-dependent results may differ by setting), and no exclusion versus the sibling basic-astro tools.

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