Astro Agents - verifiable planetary timing data and astrology

Complete Vedic report

vedic_report

Read-onlyIdempotent

Vedic astrology report in one call: kundli, Vimshottari dashas, doshas and the birth panchang. The full Jyotish dossier for one person in a single deterministic call: everything in /vedic/kundli, /vedic/dashas (2 levels, running periods with on_date), /vedic/doshas and the panchang at birth. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.50 per call via REST POST https://astro-agent.dev/v1/vedic/report (x402 or MPP); always paid, never a free call.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "vedic_report"
  }
}

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).
`on_date`	No	YYYY-MM-DD (UTC): also report what is active on this date.
`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`	No	Provenance of the result.
`error`	No	x402 offer only: why payment is required.
`result`	No	The calculation result.
`accepts`	No	x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...).
`endpoint`	No	The REST route that computed it, e.g. 'western/natal'.
`resource`	No	x402 offer only: the resource being paid for.
`extensions`	No	x402 offer only: protocol extensions (bazaar).
`x402Version`	No	x402 offer only: protocol version (2).

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 3, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "endpoint",
+      "result",
+      "meta"
+    ]
+  },
+  {
+    "required": [
+      "x402Version",
+      "accepts"
+    ]
+  }
+]

addedOutput schema / properties / accepts

Added value: +{
+  "description": "x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...).",
+  "items": {
+    "type": "object"
+  },
+  "minItems": 1,
+  "type": "array"
+}

addedOutput schema / properties / error

Added value: +{
+  "description": "x402 offer only: why payment is required.",
+  "type": "string"
+}

addedOutput schema / properties / extensions

Added value: +{
+  "description": "x402 offer only: protocol extensions (bazaar).",
+  "type": "object"
+}

addedOutput schema / properties / resource

Added value: +{
+  "description": "x402 offer only: the resource being paid for.",
+  "type": "object"
+}

addedOutput schema / properties / x402Version

Added value: +{
+  "description": "x402 offer only: protocol version (2).",
+  "type": "integer"
+}

removedOutput schema / required

Removed value: -[
-  "endpoint",
-  "result",
-  "meta"
-]

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"
+        },
+        "dasha": {
+          "description": "Vimshottari dasha: system, year length, depth, balance at birth, the mahadashas with their antar and pratyantar periods and exact dates, and the periods running now ('current').",
+          "type": "object"
+        },
+        "doshas": {
+          "description": "Manglik (Kuja), Kaal Sarp and Sade Sati / Dhaiya, each with whether it applies, the rule used and the relevant dates.",
+          "type": "object"
+        },
+        "grahas": {
+          "description": "The nine grahas (Sun to Ketu): sidereal longitude, rashi, sign lord, nakshatra, pada, nakshatra lord, deity, house, and dignity flags.",
+          "type": "array"
+        },
+        "janma_panchang": {
+          "description": "The panchang at birth: tithi, nakshatra, yoga, karana and vara.",
+          "type": "object"
+        },
+        "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": "Divisional charts D1 (rashi) and D9 (navamsa), keyed by name.",
+          "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",
+        "dasha",
+        "doshas",
+        "janma_panchang"
+      ],
+      "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 cover read-only, idempotent and non-destructive semantics, and the description adds substantial context beyond them: determinism (JPL DE440, no LLM), a verifiable meta.result_sha256 on every result, and a $0.50 per-call price with x402/MPP payment. It does not cover what happens on payment failure or whether a failed/declined call is still charged, which is the main behavioral gap for a paid 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 deliverable, then pricing and determinism, which is the right order for a paid tool. There is some redundancy ('in one call' / 'single deterministic call', and the endpoint enumeration restates the opening list), but no sentence is wasted.

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?

With an output schema present, return values need not be described, and the description covers cost, payment rails, determinism and verification. What is left unaddressed is the notable fact that only latitude/longitude are required (birth date-time is optional) and how the report degrades without it — a gap worth one line given the tool's complexity.

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%, so the schema already documents all ten parameters including enums and defaults; baseline is 3. The description adds only marginal meaning, clarifying that dashas are returned at 2 levels by default and that on_date reports what is running on that date — useful but limited.

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 composite deliverable: kundli, Vimshottari dashas, doshas and birth panchang in one call. It explicitly distinguishes itself from the sibling tools (kundli, doshas, vimshottari_dasha, panchang) by naming the exact endpoint contents it bundles, so an agent can tell it is the aggregate rather than any single component.

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?

Usage context is clear: use this when you want the full dossier in a single call rather than hitting the individual endpoints. The 'always paid, never a free call' line implicitly routes cost-sensitive callers to the free siblings, but the description never states that alternative explicitly or names which sibling to use for a narrower question.

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

All Astro Agents - verifiable planetary timing data and 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.