Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_nakshatra

Read-onlyIdempotent

Retrieves lunar mansion (nakshatra) details for a date and location, including current nakshatra, start/end times, ruling lord, and related astrological information.

Instructions

Get nakshatra (lunar mansion) details for a given date and location.

Returns the current nakshatra, its start/end time, lord, and related details.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, open-world lookup. The description adds that it returns the current nakshatra with start/end time and lord, but does not add meaningful behavioral context such as error behavior, timezone handling, or how location affects the result.

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 definition is short and front-loaded, with the core action stated first and return details second. The phrase 'and related details' is vague, but the overall structure is efficient.

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?

For a read-only lookup with an output schema and strong annotations, the description is adequate in stating purpose and return contents. However, it omits important input context such as the required timezone and does not help the agent choose between this and closely related nakshatra tools.

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?

Schema description coverage is reported as 0%, and the single top-level parameter is actually a PanchangInput object requiring day, month, year, place, lat, lon, and tzone. The description only says 'date and location' and does not explain the required fields, timezone format, or language semantics, so it does not compensate for the schema coverage gap.

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 and resource: get nakshatra (lunar mansion) details for a date and location. It is clear what the tool does, but it does not distinguish itself from nearby tools such as divine_get_surya_nakshatra or the month nakshatra list tools.

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?

The phrase 'for a given date and location' implies the usage context, but there is no explicit when-to-use guidance, no exclusions, and no routing to alternatives such as surya nakshatra or month-long nakshatra listings.

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