AstroWay Astrology API (full catalogue)

Life-area timing: education

astroway_vedic_timing_education

Read-onlyIdempotent

Education windows from the 4th and 5th houses, their lords and the karakas Mercury and Jupiter, 9th supporting; KP group 4, 9, 11. 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. Rao, basis modern): Jupiter and Saturn both occupy or aspect a primary house or the sign of its lord.

[Group: Vedic] [Endpoint: POST /v1/vedic/timing/education] [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_education"
  }
}

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

A4.2/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description still adds genuine behavior: windows are cut at every Vimshottari period change (level-controlled) and every Jupiter or Saturn sign change. It also discloses the output shape per window (score, components dasha/transit/kp, fired rules, basis, source key) and names the modern double-transit rule with its source lineage.

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

Conciseness5/5

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

Two front-loaded sentences and a parenthetical: houses and karakas first, then window-generation mechanics, then output shape, then the named transit rule. No filler, no repetition of the endpoint or cost metadata.

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?

For a moderately complex timing tool with a full output schema and clear annotations, this covers everything an agent needs to call it correctly: what it scores, how windows are segmented, what `level` changes, and what the scored result contains. Nothing material is left to guesswork.

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 schema already documents `years`, `fromDate`, `level`, `kp` and `minScore`. The description adds meaning the schema does not: it explains that `level` determines where windows are cut (pratyantar by default, antar for coarser cuts), which is the real consequence of that parameter. It restates the years/fromDate ranges without adding syntax beyond the schema.

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?

States a specific verb+resource: it derives education timing windows from the 4th/5th houses, their lords, Mercury and Jupiter, with the 9th supporting and KP group 4/9/11. That is far more precise than the title alone. It never names a sibling (e.g. astroway_vedic_timing_all or astroway_vedic_timing_career) to contrast against, so differentiation is only implicit through the word 'education'.

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 by the mechanics: scan a span of `years` from `fromDate` and get scored windows. There is no explicit statement of when to pick this over astroway_vedic_timing_all, astroway_vedic_muhurat_education_start, or the other life-area timing tools, and no prerequisites or exclusions are given.

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?