Birthstar Vedic Astrology MCP

get_day_periods

Get sunrise/sunset and the auspicious/inauspicious windows of the BIRTH day.

Rahu kala, Yamaganda, Gulika kala, Abhijit and Brahma muhurta, plus true
sunrise/sunset, day length and whether the birth was by day.

IMPORTANT: these are the windows for the DATE OF BIRTH, not for today. This
tool cannot answer "when is Rahu kala today" — that needs a chart created
for today's date.

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": {
      "chart_id": "<chart_id>"
    },
    "name": "get_day_periods"
  }
}

Input Schema

Name	Required	Description	Default
`chart_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose the key behavior: it returns birth-day windows, day length, and a day/night indicator. The warning about not answering today's periods is useful behavioral context beyond a bare 'Get'. It does not mention output format or edge cases, but those are not critical for this simple read-style tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences front-load the purpose, then list the exact contents, then deliver the caveat. Every sentence adds information; the step-by-step progression is efficient and easy to parse.

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 a one-parameter tool with no output schema, the description covers what the tool returns, the birth-day scope, and the common misuse case. It is slightly incomplete only in not describing the response shape or the source of chart_id, but these are minor against the explicit content listing.

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 0%, so the description must compensate. It never explicitly defines chart_id, but the phrase 'of the BIRTH day' and the DATE OF BIRTH warning imply chart_id identifies the chart whose birth day should be analyzed. This is adequate for a single obvious parameter, though explicit 'chart_id is the chart to use' would be stronger.

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 and resource ('Get sunrise/sunset and the auspicious/inauspicious windows of the BIRTH day') and enumerates exactly which windows are returned (Rahu kala, Yamaganda, Gulika kala, Abhijit, Brahma muhurta). The repeated emphasis on 'BIRTH day' vs 'today' distinguishes it from time-oriented siblings like get_panchanga.

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?

Gives an explicit when-not: 'these are the windows for the DATE OF BIRTH, not for today.' It also states the alternative path: answering today's Rahu kala 'needs a chart created for today's date,' preventing an agent from misusing this tool for current-day queries.

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

All Birthstar Vedic Astrology MCP 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?