Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_kp_planetary_sub

Read-onlyIdempotent

Retrieve KP planetary sub lords for every planet, including house ownership, nakshatra sub and sub-sub lords, conjunctions, and aspects to support KP-based event prediction.

Instructions

Get KP Planetary Sub Lords for all planets, with each planet's conjunctions and aspects.

Returns table_data with one row per planet: the house it sits in and the houses it owns, plus its nakshatra (star), sub and sub-sub lords with theirs. Essential for KP-based event prediction. Each row also has: conjunction (planets within 5 degrees), aspected_by (planets aspecting it), and aspect_to with the planets and house cusps it aspects.

KP aspects are Vedic aspects measured by degree. Every planet aspects the 7th (180 degrees); Mars also the 4th and 8th, Jupiter the 5th and 9th, Saturn the 3rd and 10th. Rahu and Ketu cast no aspect. Orb is 8 degrees (Moon 12; Uranus, Neptune and Pluto 5).

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

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

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. Beyond that, the description adds substantial behavioral context: the table_data row structure, conjunction threshold of 5 degrees, aspect definitions by planet, Rahu/Ketu exceptions, and orb values. It does not cover error behavior or node_type effects, but the added calculation semantics are strong.

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 description is front-loaded with purpose and return structure, then supplies aspect rules that are useful for interpreting results. It is somewhat detailed, but the detail is domain-specific and earns its place rather than being filler.

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?

The tool has a rich input schema, annotations, and an output schema, so the description does not need to repeat all field definitions. It still provides enough return-shape and aspect-rule context for an agent to understand what the tool produces. The main gap is the lack of explicit guidance about sibling alternatives.

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%, and both parameters are documented in the input schema. The description adds no additional parameter guidance, such as how node_type affects the planetary sub lord calculations, so baseline 3 is appropriate.

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 clearly states a specific verb and resource: retrieving KP planetary sub lords for all planets, including conjunctions and aspects. It is distinguishable by its focus on planetary sub/sub-sub lords and aspects, but it does not explicitly contrast itself with sibling tools such as KP planetary positions or cuspal sub 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 description implies usage through 'Essential for KP-based event prediction,' giving a domain context for when to use it. However, it does not state when not to use it or name alternative sibling tools for related KP calculations.

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