Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_graha_drishti

Read-onlyIdempotent

Calculate Vedic planetary aspects (Graha Drishti) for a birth chart, showing which planets aspect which houses and planets using Parashari whole-sign rules.

Instructions

Get Graha Drishti (Vedic planetary aspects) for a birth chart: which planets aspect which houses and planets.

Parashari drishti on whole-sign houses counted from the Lagna. Every graha aspects the 7th house from itself; Mars also the 4th and 8th, Jupiter the 5th and 9th, Saturn the 3rd and 10th, and Rahu and Ketu the 5th and 9th. Covers the nine grahas Sun to Ketu; Uranus, Neptune and Pluto have no drishti and are left out.

Returns planets (name, sign, house, aspects: each with the aspect number, target house, its sign and the planets in it; aspected_by: planet and aspect number) and houses (house, sign, planets in it, aspected_by). Names are returned in English regardless of lan. node_type only changes where Rahu and Ketu fall.

This is not the KP aspect data in divine_get_kp_planetary_sub, which measures aspects in degrees with an orb and gives Rahu and Ketu none.

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

Input Schema

NameRequiredDescriptionDefault
paramsYesBirth details
node_typeNoRahu/Ketu calculation method: 'meannode' (default) or 'truenode'

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.15.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered; the description adds substantive domain behavior beyond them – the counting convention (whole-sign houses from Lagna), the exact aspect assignments per graha, and the deliberate exclusion of Uranus, Neptune and Pluto. It stops short of noting any auth or rate-limit behavior, but for a read-only calculation tool the methodological disclosure is the useful part.

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?

Front-loaded with the purpose and scoped correctly, with no filler sentences; the astrological rules are dense but each clause carries information. Minor deduction because the returns paragraph largely restates what the output schema already declares, and the raw line breaks interrupt sentences mid-phrase.

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

Completeness5/5

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

Given a birth-detail-only input, a full output schema, and read-only annotations, an agent has everything needed: required inputs, the meaning of the optional node_type, the calculation convention, and the sibling it differs from. Nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns above that by clarifying the one non-obvious parameter: node_type 'only changes where Rahu and Ketu fall', which tells the agent the impact is scoped to two planets. It also qualifies the lan parameter by noting names come back in English regardless of lan, a caveat absent from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Get Graha Drishti (Vedic planetary aspects) for a birth chart') and narrows the scope to which planets aspect which houses and planets, immediately separating it from degree-based aspect tools. The named rule set (Parashari, whole-sign, 7th-house base with Mars 4/8, Jupiter 5/9, Saturn 3/10, Rahu/Ketu 5/9) makes the tool unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative divine_get_kp_planetary_sub and states the discriminating condition: KP measures aspects in degrees with an orb and assigns Rahu/Ketu none, whereas this tool uses Parashari whole-sign drishti with nodal aspects. That is a genuine when-to-use-this-instead-of-that instruction rather than implied usage.

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