AstroWay Astrology API (full catalogue)

Life-area timing: career

astroway_vedic_timing_career

Read-onlyIdempotent

Career windows (job change, promotion) from the 10th house, its lord and the karakas Sun and Saturn, 6th, 11th and 2nd supporting; KP group 2, 6, 10, 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.

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

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.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the output contract: each window carries score, components (dasha, transit, kp), fired rules, basis and a source key into sources, plus the window-cutting logic at Vimshottari and Jupiter/Saturn sign changes. The description is cut off mid-sentence at 'Double transit (K.N.', so the behavioral picture is incomplete but still well past what the annotations provide.

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?

Purpose is front-loaded in the first clause, but the opening is a dense run of astrological jargon (house lists, karakas, KP group numbers) that is hard to parse, and the text terminates mid-sentence, indicating truncation. It is compact, but the density and the cut-off tail cost it.

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 Tier-3, 50-credit tool with an output schema, the description does enough: it explains the derivation, the window-cutting rule, the parameters' effects and the shape of each window, so return values need not be spelled out. The truncated final sentence and the absence of any comparison against astroway_vedic_timing_all leave a small gap.

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 years (1-20, default 5), level (antar/pratyantar), fromDate and kp. The description restates years, fromDate and level and ties level to window granularity, but adds little that the schema does not already say; 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?

The description opens with a concrete verb+resource: career windows (job change, promotion) derived from the 10th house, its lord, and the Sun/Saturn karakas. That scope distinguishes it cleanly from the other life-area timing siblings (marriage, children, education, property, foreign, all) without either schema being opened.

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 career framing implies the use case, but there is no explicit statement of when to pick this over astroway_vedic_timing_all or the other astroway_vedic_timing_* tools, and no prerequisites or exclusions are given. Usage is inferable from the name and topic rather than stated.

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?