Asterwise

Tarabala and Chandrabala

asterwise_get_tarabala

Read-onlyIdempotent

Tarabala and Chandrabala for any date, with the Moon's star and sign change times. For 1 to 31 civil days, every Moon nakshatra and Moon sign with exact start and end (local and UTC), the tara counted from the birth nakshatra with its name and verdict, and the Moon's house from the natal Moon with the chandrabala verdict (Muhurta Chintamani).

WORKFLOW: BEFORE: asterwise_get_natal_chart — the birth Moon's star. AFTER: asterwise_get_vedic_daily_factors — every other factor of the day.

INPUT CONTRACT: birth — BirthData. target_date (optional YYYY-MM-DD) — first day; defaults to today in the birth timezone. days (1-31, default 1). target_timezone (optional IANA) — defines the civil days; defaults to the birth timezone.

DO NOT CONFUSE WITH: asterwise_get_nakshatra_prediction — a one-day prediction, not timed spans. asterwise_get_gochar — all planets from the Moon, not the Moon's own tara.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-tarabala/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Number of civil days, 1 to 31.
`birth`	Yes	Birth data for a single person.
`target_date`	No	First day, YYYY-MM-DD. Defaults to today in the birth timezone.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown
`target_timezone`	No	IANA timezone that defines the days. Defaults to the birth timezone.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: exact start/end times in local and UTC, day-count bounds, timezone-driven civil-day definition, default source timezone, and the interpretive system used (Muhurta Chintamani). It omits error handling, but defers to a documentation link.

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?

Front-loaded purpose sentence, then labeled blocks (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH) that are scannable. Slightly dense and verbose given the schema already carries parameter detail, but every section has a clear function.

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?

Covers purpose, sequencing, parameter contract, and sibling disambiguation, and an output schema exists so return values need not be explained. Only gap is behavior on failure/limits, which is punted to an external URL.

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 baseline is 3. The INPUT CONTRACT mostly restates schema facts (defaults, ranges, IANA format) rather than adding new semantics; the only mild value-add is clarifying that target_timezone defines the civil days.

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?

States a specific verb+resource: computes Tarabala and Chandrabala for any date, plus the Moon's star/sign change times for 1-31 civil days. It enumerates the outputs (nakshatra spans, tara from birth star, Moon house with chandrabala verdict) and cites the source text, so it is unmistakable against siblings.

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

Usage Guidelines5/5

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

Explicit workflow (BEFORE: get_natal_chart for the birth Moon star; AFTER: get_vedic_daily_factors) plus a DO NOT CONFUSE WITH block naming two alternatives and the distinguishing criterion for each. Nothing is left to inference.

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

All Asterwise tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?