AstroWay Vedic astrology

Panchang: Tara Bala for a person

astroway_vedic_panchang_tara_bala

Read-onlyIdempotent

For each day (sunrise to next sunrise) and each nakshatra in it: the count from the birth star, the tara (Janma, Sampat, Vipat, Kshema, Pratyak, Sadhaka, Vadha, Mitra, Parama Mitra), its quality and favourable. Birth star from birth or janmaNakshatra; days 1 to 31.

[Group: Vedic] [Endpoint: POST /v1/vedic/panchang/tara-bala] [Required: date, 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>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_vedic_panchang_tara_bala"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Civil date, YYYY-MM-DD. The day runs from its sunrise to the next sunrise.
`days`	No	Number of days from date, 1 to 31. Default 1.
`birth`	No
`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.
`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
`janmaRashi`	No	Natal Moon sign, when birth is not sent: Mesha ... Meena.
`janmaNakshatra`	No	Birth star 1 (Ashwini) to 27 (Revati), when birth is not sent.
`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
`days`	No
`rule`	No
`method`	No
`janmaNakshatra`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured facts: the endpoint, the required trio (date, latitude, longitude) and a 20-credit Tier 2 cost, which matters for an agent budgeting calls. It does not say what happens if both `birth` and `janmaNakshatra` are supplied, nor whether the birth star derivation is sidereal per the request ayanamsa.

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 output shape is front-loaded in one dense sentence, followed by bracketed metadata for group, endpoint, required fields and cost, which is easy to scan. The enumerated tara list is long but earns its place by naming the vocabulary the response uses. No filler sentences.

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 the description's coverage of return contents is a bonus rather than a requirement, and annotations handle safety. However, for a 13-parameter tool with a nested `birth` object, an agent still lacks the interaction rule between `birth` and `janmaNakshatra`, whether coordinates are required for the transit location or the natal chart, and any scenario guidance. Adequate but with clear gaps.

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 coverage is 69%, so the baseline is a 3, and the description roughly matches it: it restates the `days` 1-31 bound already in the schema and clarifies the birth-star source (`birth` object or the 1-27 `janmaNakshatra` integer), which is a real disambiguation. It says nothing about the undescribed latitude/longitude parameters, the timezone/timezoneOffset trade-off, or when to use `fields`/`precision` compact mode, so it does not compensate for the coverage gap.

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 the specific resource precisely: per day and per nakshatra, the count from the birth star and its tara (with the nine tara names enumerated) plus quality and `favourable`. An agent can tell this is star-based strength relative to a natal star, not a generic panchang dump. It stops short of differentiating from sibling panchang tools such as astroway_vedic_panchang_chandra_bala or chandrashtama, which also produce per-day personal strength.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement: nothing says to pick this for star-based day quality versus chandra_bala for Moon-sign quality, or versus the muhurat family for picking an event date. The only guidance-adjacent line says the birth star comes from `birth` or `janmaNakshatra`, which is parameter routing rather than usage context. An agent must already know Vedic terminology to place this tool.

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?