AstroWay Astrology API (full catalogue)

Life-area timing: property and vehicles

astroway_vedic_timing_property

Read-onlyIdempotent

Property and vehicle windows from the 4th house, its lord and the karakas Mars (land) and Venus (vehicles), 11th supporting; KP group 4, 11, 12. Windows over years (1 to 20, default 5) from fromDate, cut at every Vimshottari period change (level pratyantar by default, or antar) and every Jupiter or Saturn sign change. Each window has score, its components (dasha, transit, kp) and every rule that fired, with basis (classical, modern, kp) and a source key into sources. Double transit (K.N.

[Group: Vedic] [Endpoint: POST /v1/vedic/timing/property] [Cost: 50 credits (Tier 3)]

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": {
      "body": "<body>"
    },
    "name": "astroway_vedic_timing_property"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	Birth data (time and coordinates required: the houses come from the Lagna) and the span to scan for one life area.
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

Name	Required	Description	Default
`area`	No
`level`	No
`natal`	No
`houses`	No
`method`	No
`window`	No
`karakas`	No
`sources`	No
`summary`	No
`windows`	No
`kpHouses`	No
`rulesBasis`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is behavioral detail, and the description delivers it: how windows are cut (every Vimshottari period change at `level`, plus every Jupiter or Saturn sign change), what each window carries (score, components, fired rules, basis, source key), and the KP significator toggle. The only blemish is the final sentence, truncated mid-word ('Double transit (K.N.'), leaving that rule unexplained.

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?

The core scope is front-loaded in the first clause, which is good, but the body is a single dense run-on packed with untranslated jargon (karakas, pratyantar, KP group) and ends in a truncated fragment. It is information-rich but not cleanly structured, and the cut-off sentence should have been removed or completed.

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?

The inputs are fully documented in the schema, and an output schema exists so return values needn't be spelled out — yet the window anatomy described here still helps the agent reason about results. What is missing is routing context against the many vedic_timing and muhurat siblings, plus the truncated double-transit rule; neither is fatal for correct invocation.

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 defines `years`, `fromDate`, `level` and `minScore` in detail, including the pratyantar-vs-antar tradeoff of fewer, longer windows. The description restates these same facts rather than adding new meaning, so baseline 3 applies. The one added nuance is that windows are cut at Jupiter/Saturn sign changes, but that is behavioral rather than parameter semantics.

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 description names a specific resource and scope: 'Property and vehicle windows from the 4th house, its lord and the karakas Mars (land) and Venus (vehicles), 11th supporting'. An agent knows this computes timing windows for property/vehicle life areas, distinct from the career or marriage siblings by subject matter. It never explicitly names the sibling timing tools though, so differentiation rests on the title and life-area wording rather than an in-description comparison.

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?

Usage is implied rather than stated: the reader must infer that this is the tool for 'when will property or vehicle matters activate' and that astroway_vedic_timing_all or the muhurat purchase tools cover other needs. There are no when-not conditions, no prerequisites, and no mention that a natal birth time is required for the houses to be meaningful — that only appears in the schema.

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

All AstroWay Astrology API (full catalogue) 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.

Resources

Need Help?