AstroWay Vedic astrology

Shadbala: Ishta and Kashta phala

astroway_vedic_shadbala_ishta_kashta

Read-onlyIdempotent

Ishta and Kashta phala of the seven grahas from Uchcha bala and Cheshta bala (virupas). parashara: BPHS 28.5-6, the shubha and ashubha rays and Ishta as half the sum, Kashta = 60 - Ishta. geometric: square root of Uchcha x Cheshta and of (60 - Uchcha) x (60 - Cheshta), the form most software prints. The Sun's and the Moon's Cheshta come from the BPHS 28.4 kendra (sayana Sun less 90°; Moon less Sun); Mars to Saturn use /vedic/shadbala/cheshta.

[Group: Vedic] [Endpoint: POST /v1/vedic/shadbala/ishta-kashta] [Required: date, time, latitude, longitude] [Cost: 20 credits (Tier 2)]

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

Input Schema

Name	Required	Description	Default
`city`	No
`date`	Yes
`name`	No
`time`	Yes
`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.
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`latitude`	Yes
`timezone`	No	IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
`cosmogram`	No
`longitude`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`ayanamsaId`	No
`zodiacType`	No
`houseSystem`	No		P
`timezoneOffset`	No	Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

Name	Required	Description	Default
`type`	No
`unit`	No
`items`	No
`sources`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds genuine domain behavior — how Ishta is derived and that it is capped by Kashta = 60 - Ishta, plus the special-case source for Sun and Moon Cheshta — but says nothing about response shape, whether both conventions are returned together, or credit cost (only present in the bracketed context block).

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?

The purpose and output are front-loaded in the first clause, followed by the two formula variants. Sentences are dense with domain notation but each carries information; the BPHS citation could be trimmed without loss for an agent, which keeps it just short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 described, and annotations cover the safety profile. For a 15-parameter tool with only 4 required and a sidereal-dependent computation, however, the description leaves untouched which settings (ayanamsa, zodiacType, timezone vs timezoneOffset) materially change the result, which is the one thing an agent cannot infer from structured fields alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% across 15 parameters; the birth-data parameters (date, time, latitude, longitude, city, name) and the calculation switches (zodiacType, houseSystem, ayanamsaId, cosmogram) carry no schema descriptions at all. The description provides zero parameter guidance and never indicates which of the optional parameters actually affect Ishta/Kashta, nor which ayanamsa matters for a sidereal Vedic computation.

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 computational output — Ishta and Kashta phala for the seven grahas — and identifies the two source components (Uchcha bala and Cheshta bala in virupas). It even points at the sibling that supplies part of the input ('Mars to Saturn use /vedic/shadbala/cheshta'), though it never contrasts this endpoint with shadbala_full or shadbala_cheshta, so an agent must infer where this fits in the Shadbala family.

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 guidance is implied rather than stated: the description explains that two derivation conventions exist ('parashara' per BPHS 28.5-6 vs 'geometric', the form most software prints), which helps an agent understand the interpretive fork. There is no explicit when-to-use/when-not guidance and no statement that a full Shadbala breakdown should be requested via shadbala_full instead.

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

All AstroWay Vedic 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.

Resources

Need Help?