Skip to main content
Glama
Divine API Indian Astrology MCP

Divine API Indian Astrology MCP

Official
by DivineAPI

divine_get_jaimini_swamsa_chart

Read-onlyIdempotent

Generate the Jaimini Swamsa chart as SVG and image by recasting Navamsa planets around the Atmakaraka’s D9 sign, with Swamsha and Lagnamsha details.

Instructions

Generate the Jaimini Swamsa chart (Navamsa from the Karakamsha) as SVG and image.

The Navamsa (D9) planets recast into houses with the Karakamsha sign (the Atmakaraka's D9 sign, Atmakaraka from the 7 planets Sun to Saturn) as house 1. divine_get_jaimini_karakamsha_lagna recasts the natal D1 planets around that sign instead. Returns atmakaraka, swamsha_sign and swamsha_sign_no, lagnamsha_sign and lagnamsha_sign_no (the D9 Ascendant), svg, and base64_image. lan translates the names, not the sign numbers; node_type only moves Rahu and Ketu in the chart.

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

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.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description earns credit for adding behavior not in structured fields: the Atmakaraka is derived from the 7 planets Sun to Saturn, and the response carries both SVG and base64 image output. It stops short of noting cost, rate limits, or computational weight for an openWorld generation tool.

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 definition and the return list, with the parameter caveats last. Dense but every clause carries information; the embedded domain jargon (Karakamsha, Atmakaraka, D9) is necessary precision rather than padding, though the formatting reads as one compressed block.

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?

An output schema exists, yet the description still disambiguates the returned fields that are easy to confuse (swamsha_sign vs. lagnamsha_sign) and explains the derivation and sibling difference. For a single-param-wrapper generation tool, nothing an agent needs to call it correctly is absent.

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 3 baseline applies, but the description genuinely improves on the schema: it clarifies that "lan translates the names, not the sign numbers" (the schema only says "Language code for response") and that "node_type only moves Rahu and Ketu in the chart," scoping a parameter the schema merely labels as a calculation method.

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?

Opens with a specific verb and resource ("Generate the Jaimini Swamsa chart") and immediately defines the computation in domain terms ("Navamsa (D9) planets recast into houses with the Karakamsha sign as house 1"). It also names the nearest sibling and states how the output differs, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

Explicitly contrasts with divine_get_jaimini_karakamsha_lagna: that tool "recasts the natal D1 planets around that sign instead." That is a clear selection rule between alternatives. What's missing is a positive when-to-use statement or any exclusion beyond this one sibling comparison.

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