Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_surya_nakshatra

Read-onlyIdempotent

Retrieve the Sun's Nakshatra for a given date and location to support solar-based astrological calculations and rashi sandhi analysis.

Instructions

Get Surya (Sun) Nakshatra details for a given date and location.

Returns the nakshatra occupied by the Sun, useful for solar-based astrological calculations and rashi sandhi analysis.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds only that the result is the Sun's nakshatra, with no notes on accuracy windows, timezone-sensitive boundary behavior, or rate limits — modest added value on top of structured data.

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 core action front-loaded before the use case. There is minor redundancy between "Surya (Sun) Nakshatra details" and "the nakshatra occupied by the Sun," but nothing that wastes meaningful space.

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?

Output schema and annotations are present, so the description needn't explain return values or safety. For a simple single-retrieval tool the description is broadly adequate, but it leaves the agent without explicit routing guidance among many closely named nakshatra siblings, which is the main remaining gap.

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 mentions "date and location," which loosely maps to the nested PanchangInput fields, but it adds no format or semantic detail beyond that. The reported coverage of 0% reflects the wrapper-level "params" property; the nested schema does document day/month/year/place/lat/lon/tzone, so the description is not fully compensating but the underlying schema is reasonably self-explanatory.

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 Surya (Sun) Nakshatra details for a given date and location," and clarifies the return concept ("the nakshatra occupied by the Sun"). It does not explicitly distinguish itself from the near siblings divine_get_nakshatra or divine_get_month_surya_nakshatra_list, so an agent must infer the difference from names alone.

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?

It offers contextual usage ("useful for solar-based astrological calculations and rashi sandhi analysis"), which implies when the tool applies. It gives no exclusions, prerequisites, or named alternatives, so the choice between this and the general nakshatra or month-list tools is left implicit.

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