Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_kp_cuspal_sub

Read-onlyIdempotent

Retrieves KP cuspal sub lords for all house cusps, including each cusp's rashi, nakshatra, sub and sub-sub lords plus aspecting planets, to support KP house predictions.

Instructions

Get KP Cuspal Sub Lords for all house cusps, with the planets aspecting each cusp.

Returns table_data with one row per cusp: the rashi, nakshatra, sub and sub-sub lords, each with the house it sits in and the houses it owns. The sub lord is the primary factor for KP predictions about that house's significations. Each row also has aspected_by, the planets that aspect that cusp.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

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 readOnly, idempotent, non-destructive behavior, so the description is free to spend its words on domain behavior instead. It does that well: it discloses the exact return shape (one row per cusp with rashi, nakshatra, sub and sub-sub lords, occupied house, owned houses, and aspected_by) and spells out the KP aspect rules including which planets cast which aspects and the per-planet orbs. The only gap is that it never says whether the calculation depends on the supplied birth details or how failures are surfaced.

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 the opening line, followed by return structure and then the aspect rules, which is a sensible order for an agent reading top-down. The aspect and orb enumeration is dense but earns its place because it defines a non-obvious domain term the response depends on. A few phrases, such as the restatement of 'aspects that cusp,' could be trimmed without loss.

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?

An output schema exists, so the description is not obligated to explain return values, yet it still gives a row-by-row account of table_data and defines aspected_by, which is more than required. Safety and idempotency are covered by annotations. The remaining omission is any mention of the required birth-detail input, which is a modest gap for a single-parameter tool.

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 says nothing about the single params object or the dozen required birth-detail fields it wraps. Top-level schema description coverage is reported as 0%, but the nested KundliInput definition does carry per-field descriptions such as 'Birth hour in 24h format' and 'Timezone offset from UTC,' so the schema largely documents itself. The description neither compensates for the gap nor adds meaning beyond the field-level text, leaving this at the minimum-viable baseline.

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 first sentence names a specific verb and resource: 'Get KP Cuspal Sub Lords for all house cusps, with the planets aspecting each cusp.' That is precise enough that an agent knows exactly what it produces. It does not, however, differentiate itself from close siblings such as divine_get_kp_cuspal or divine_get_kp_cuspal_significator, so an agent choosing between those 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?

The description implies a use case with 'The sub lord is the primary factor for KP predictions about that house's significations,' which tells the agent when the output matters. It never states when to prefer this tool over the cuspal or significator siblings, and there are no exclusions or prerequisites. Usage is implied rather than directed.

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