Astro Agents - deterministic Western + Vedic astrology

Kundli with all 16 vargas

kundli_full

Read-onlyIdempotent

Vedic astrology full kundli: all 16 Shodashavarga divisional charts, D1 to D60 (navamsa, dasamsa...), by Parashara's rules. Everything in /vedic/kundli plus D1, D2, D3, D4, D7, D9, D10, D12, D16, D20, D24, D27, D30, D40, D45 and D60, each with its lagna, placements and house table. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.32 per call via REST POST https://astro-agent.dev/v1/vedic/kundli-full (x402 or MPP); your first 3 calls are free here.

Input Schema

Name	Required	Description	Default
`date`	No	YYYY-MM-DD (use with 'time' instead of 'datetime').
`time`	No	HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning).
`options`	No	Optional calculation settings; every default is the common Parashari convention.
`datetime`	No	Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'.
`latitude`	Yes	Decimal degrees, north positive.
`timezone`	No	IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date.
`longitude`	Yes	Decimal degrees, east positive.
`time_basis`	No	What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time.	civil
`ambiguous_time`	No	Which occurrence to use when a local time happens twice (DST fall-back).	earlier

Output Schema

Name	Required	Description
`meta`	Yes	Provenance of the result.
`result`	Yes	The calculation result.
`endpoint`	Yes	The REST route that computed it, e.g. 'western/natal'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "endpoint": {
+      "description": "The REST route that computed it, e.g. 'western/natal'.",
+      "type": "string"
+    },
+    "meta": {
+      "description": "Provenance of the result.",
+      "properties": {
+        "astronomy_library": {
+          "description": "Astronomy library and version.",
+          "type": "string"
+        },
+        "compute_ms": {
+          "description": "Computation time in milliseconds.",
+          "type": "number"
+        },
+        "computed_at": {
+          "description": "When it was computed (UTC, ISO 8601).",
+          "type": "string"
+        },
+        "deterministic": {
+          "description": "Always true: same input, same result.",
+          "type": "boolean"
+        },
+        "engine": {
+          "description": "Engine name and version.",
+          "type": "string"
+        },
+        "ephemeris": {
+          "description": "Ephemeris used (NASA/JPL DE440).",
+          "type": "string"
+        },
+        "frame": {
+          "description": "Reference frame of the positions.",
+          "type": "string"
+        },
+        "input_sha256": {
+          "description": "SHA-256 of the canonical input.",
+          "type": "string"
+        },
+        "llm_used": {
+          "description": "Always false: no language model is involved.",
+          "type": "boolean"
+        },
+        "payment": {
+          "description": "How this call was paid: protocol ('free' or 'none'), price and the free calls remaining.",
+          "type": "object"
+        },
+        "reproducibility": {
+          "description": "How to reproduce and check this result.",
+          "type": "string"
+        },
+        "result_sha256": {
+          "description": "SHA-256 of the canonical 'result'; check it with verify_result_hash.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "engine",
+        "deterministic",
+        "llm_used",
+        "input_sha256",
+        "result_sha256"
+      ],
+      "type": "object"
+    },
+    "result": {
+      "description": "The calculation result.",
+      "properties": {
+        "bhavas": {
+          "description": "The twelve houses (bhavas): sign, rashi, lord and the grahas occupying each one.",
+          "type": "array"
+        },
+        "grahas": {
+          "description": "The nine grahas (Sun to Ketu): sidereal longitude, rashi, sign lord, nakshatra, pada, nakshatra lord, deity, house, and dignity flags.",
+          "type": "array"
+        },
+        "lagna": {
+          "description": "The ascendant (lagna): sidereal longitude, rashi and sign, degree, sign lord, nakshatra, pada and nakshatra lord.",
+          "type": "object"
+        },
+        "settings": {
+          "description": "Settings applied: sidereal zodiac, ayanamsa (name and value in degrees), lunar node type, house system and divisional-chart rules.",
+          "type": "object"
+        },
+        "subject": {
+          "description": "The resolved input: 'time' (local input, time zone and historical UTC offset, UT, Julian days, Delta T) and, when given, 'location' (latitude, longitude).",
+          "type": "object"
+        },
+        "summary": {
+          "description": "Key facts: lagna sign and lord, Moon sign, sidereal Sun sign, janma nakshatra with pada and lord, and the exalted, debilitated, retrograde and combust grahas.",
+          "type": "object"
+        },
+        "vargas": {
+          "description": "All 16 Shodashavarga divisional charts, D1 to D60, keyed by name (D1, D2, D3, D4, D7, D9, D10, D12, D16, D20, D24, D27, D30, D40, D45, D60).",
+          "type": "object"
+        },
+        "warnings": {
+          "description": "Notes on the input or the calculation (for example an assumed noon for an unknown birth time). Present only when there is something to say.",
+          "type": "array"
+        }
+      },
+      "required": [
+        "subject",
+        "settings",
+        "lagna",
+        "grahas",
+        "bhavas",
+        "summary",
+        "vargas"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "endpoint",
+    "result",
+    "meta"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedOct 5, 2026

addedInput schema / properties / options / description

Added value: +"Optional calculation settings; every default is the common Parashari convention."

addedInput schema / properties / options / properties / ayanamsa / description

Added value: +"Sidereal reference (ayanamsa). Default 'lahiri' (Chitrapaksha), the Indian standard."

addedInput schema / properties / options / properties / include_outer_planets / description
```
Added value: +"Also return Uranus, Neptune and Pluto (not used in classical Jyotish)."
```

First observedOct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered and the description correctly adds non-obvious traits instead: deterministic computation (JPL DE440, no LLM), a verifiable meta.result_sha256 on every result, and the $0.32-per-call paid model behind x402/MPP. That is real invocation-relevant context (cost/payment/auth) beyond the structured fields. It does not discuss failure modes (e.g. what happens with unknown birth time beyond the schema note), so not a 5.

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 paragraph is front-loaded with the deliverable (16 vargas, D-list) before the computation and pricing details, and every clause carries information. The closing price/endpoint/free-tier sentence is commercial but genuinely relevant to invocation. Slightly dense and list-heavy rather than wasteful.

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?

For a 9-parameter tool with a full output schema and complete annotations, the description supplies what structured fields cannot: the exact chart set returned, determinism/reproducibility guarantees, cost and payment channel. The relative positioning versus the sibling 'kundli' is implied rather than spelled out, but nothing essential to calling it correctly is missing.

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?

All 9 parameters carry schema descriptions (100% coverage), including enums, defaults and the date/time vs datetime alternatives, so the description need not repeat them. The description adds only the scope claim ('everything in /vedic/kundli plus...') and no parameter-level meaning. Baseline 3 applies when the schema does the heavy lifting.

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?

The description names a specific verb/resource ('Vedic astrology full kundli') and enumerates exactly what is produced: all 16 Shodashavarga charts D1–D60, each with lagna, placements and house table. It also differentiates from the sibling 'kundli' by stating it contains 'everything in /vedic/kundli plus' the divisional charts, so an agent can pick between them without opening a 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?

It gives clear context for selection: use this when you need the full 16-varga set rather than the base kundli, since it is a superset of /vedic/kundli. It also flags the invocation channel (REST POST endpoint, x402/MPP payment, first 3 calls free). It stops short of an explicit 'do not use this if you only need D1' exclusion, so it is clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Astro Agents - deterministic Western + Vedic astrology tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.