AstroWay Astrology API (full catalogue)

Panchang: Chandra Bala for a person

astroway_vedic_panchang_chandra_bala

Read-onlyIdempotent

For each day and each Moon sign in it: the Moon's house from the natal Moon sign, favourable (1, 3, 6, 7, 10, 11) and chandrashtama (8). Natal Moon from birth or janmaRashi; days 1 to 31.

[Group: Vedic] [Endpoint: POST /v1/vedic/panchang/chandra-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_chandra_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
`janmaRashi`	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 declare this a read-only, idempotent, non-destructive, closed-world call, so the safety profile needs no restating. The description instead adds behavior an agent could not get elsewhere: the exact classification rule, which input supplies the natal Moon, the 1–31 day range, plus the endpoint and the 20-credit Tier 2 cost. With annotations carrying the safety profile, this is solid added context.

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 core sentence is front-loaded and dense with decision-relevant facts — no filler. The bracketed Group/Endpoint/Required/Cost block is boilerplate but genuinely useful for cost and routing. Only mild terseness (backticked fragments rather than full clauses) costs it a point.

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. Still, for a 13-parameter tool the description is thin on the birth-versus-janmaRashi decision (which wins when both are sent, what happens if neither is) and on whether `janmaNakshatra` is accepted here. Complete enough to call, but not fully self-sufficient.

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 69%, so the schema does most of the documenting. The description adds real meaning on one point: natal Moon is derived from `birth` or `janmaRashi`, giving an agent the source precedence. It says nothing about the remaining parameters (`fields`, `precision`, ayanamsa, timezone, `janmaNakshatra`), though those are covered in 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?

The description states a specific computation: for each day and each Moon sign, the Moon's house counted from the natal Moon sign, with the `favourable` (1, 3, 6, 7, 10, 11) and `chandrashtama` (8) classification spelled out. That is far more than a restatement of the name. It does not, however, distinguish this from the sibling chandrashtama tools (astroway_vedic_panchang_chandrashtama, ..._chandrashtama_day) or from tara_bala, so the boundary is only implied.

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: an agent can infer the tool answers 'is this day good or bad for this person, Moon-wise'. The one explicit routing hint is that the natal Moon comes from `birth` or `janmaRashi`, which is useful. There is no when-not-to-use guidance and no pointer to the overlapping chandrashtama siblings.

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?