Astro Agents - verifiable planetary timing data and astrology

KP chart (Krishnamurti Paddhati)

kp_chart

Read-onlyIdempotent

KP astrology (Krishnamurti Paddhati) chart: the star lord, sub-lord and sub-sub-lord of every planet and house cusp, cuspal sub-lords and the A/B/C/D house significators. Krishnamurti Paddhati on the KP ayanamsa with Placidus cusps: for each of the 9 grahas and 12 cusps the sign lord, star (nakshatra) lord, sub-lord, sub-sub-lord and number among the 249 KP subs; the cuspal sub-lords; house significators at the four levels A (in the star of occupants), B (occupants), C (in the star of the lord), D (lord); and each planet's significations. The sub-division rule is stated in the response. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.15 per call via REST POST https://astro-agent.dev/v1/vedic/kp (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": "kp_chart"
  }
}

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 KP settings. Cusps are always Placidus (the KP 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"
-]

AddedOct 27, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: determinism (JPL DE440, no LLM), a verifiable meta.result_sha256, a stated sub-division rule in the response, and explicit cost/access model ($0.15 per call, x402 or MPP, never free). Cost and payment mechanism are exactly the kind of operational trait an agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the most important content, but the second sentence largely re-enumerates the star/sub/sub-sub-lord and significator lists already given in the first, repeating 'Krishnamurti Paddhati' three times. The pricing/endpoint sentence is valuable but sits awkwardly appended to an output description.

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 return values need not be spelled out, and the description still flags the hash field and the in-response sub-division rule. Combined with annotations and full schema coverage, an agent has everything needed to invoke it correctly; only the absence of explicit sibling routing keeps it from a 5.

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 the schema already documents date/time/datetime alternatives, the TIME_UNKNOWN fallback, ayanamsa defaults, and time_basis. The description adds little beyond restating that cusps are always Placidus and the KP ayanamsa is the default, both of which also appear in the schema, so the baseline 3 applies.

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 resource (KP/Krishnamurti Paddhati chart) and enumerates exactly what it returns: star lord, sub-lord, sub-sub-lord, 249 subs, cuspal sub-lords, and A/B/C/D significators. The KP-specific vocabulary makes it plainly distinguishable from siblings like kundli, natal_chart, and nakshatras without opening any schema.

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 via the KP framework (Placidus cusps, KP ayanamsa) and states it is always a paid call, which is a useful precondition. However, it never explicitly says when to choose this over natal_chart, kundli, or planet_positions, and gives no when-not guidance.

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.