AstroWay Vedic astrology

Panchang: Chandrashtama for a person

astroway_vedic_panchang_chandrashtama

Read-onlyIdempotent

Spans when the Moon transits the 8th sign from the natal Moon sign, over days (1 to 366) from date. Natal Moon from birth or janmaRashi. Each span keeps its full start and end.

[Group: Vedic] [Endpoint: POST /v1/vedic/panchang/chandrashtama] [Required: date] [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>"
    },
    "name": "astroway_vedic_panchang_chandrashtama"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	First day of the range, YYYY-MM-DD, from local midnight.
`days`	No	Length of the range in days, 1 to 366. Default 30.
`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.
`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.
`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
`rule`	No
`range`	No
`method`	No
`periods`	No
`janmaRashi`	No
`chandrashtamaRashi`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world, and the description stays consistent with them. Beyond that it adds genuinely useful behavior: spans are reported whole rather than clipped to the requested range, the natal Moon is derived rather than supplied directly, and the cost is disclosed as 20 credits (Tier 2).

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 behavioral sentence is front-loaded and dense, with each clause carrying information (span definition, range, natal Moon source, span integrity). The bracketed Group/Endpoint/Required/Cost block is boilerplate but cheap and useful, so nothing needs cutting.

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 an 11-parameter tool with a nested birth object whose schema is richly documented and an output schema that covers return values, the description gives enough to call this correctly. The only gap is that janmaNakshatra, a permitted alternative natal input, is not mentioned in the prose.

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 82%, so the schema already documents date, days, birth, janmaRashi, fields and precision. The description restates the days bound and adds only the mild clarification that the natal Moon comes from birth or janmaRashi — an either/or the schema hints at but does not state outright. It omits janmaNakshatra entirely, so it does not meaningfully exceed the schema baseline.

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 precise subject — the windows when the Moon transits the 8th sign from the natal Moon — over an explicit date span, and notes each span keeps its full start and end. That scope distinguishes it in substance from the single-day sibling astroway_vedic_panchang_chandrashtama_day, though it never names that sibling explicitly.

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 only implied: the phrase 'over `days` (1 to 366) from `date`' makes clear this is a range scan, and 'Natal Moon from `birth` or `janmaRashi`' tells the agent which input branch to supply. There is no explicit when-to-use versus the day variant, the sade-sati/chandra-bala siblings, or any stated prerequisite or exclusion.

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?