AstroCalc: Vedic astrology

What life phase each person is in, and what changes next

my_family_phases

Read-onlyIdempotent

For one saved person or everyone saved on the account: the life chapter they are in now (Vimshottari Mahadasha) and the current phase within it (Antardasha), with dates, plus what comes next and when, sorted by whose phase changes soonest. Use when the user asks why life feels stuck or is shifting, when things will change, what is changing for someone this year, or about timing for family members. Read-only. Only for people saved on the user's AstroCalc account (needs a free AstroCalc sign-in); birth details typed in the chat work without sign-in in free_kundli, kundli_milan, explain_dasha, full_chart and life_timeline.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_family_phases"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the text fields: 'en' (English, default) or 'hi' (Hindi).
`profile`	No	A saved kundli on the user's AstroCalc account: its name as listed by my_profiles (e.g. 'Mummy') or its id. Omit for all saved kundlis.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.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 the description redundantly repeats 'Read-only' rather than adding to it. However, it does add genuinely new behavioral context: an account-sign-in requirement, saved-profile-only scope, and result sorting by soonest phase change.

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 with the core answer and the routing constraint, with no filler sentences. The first sentence is dense with stacked parentheticals, and the trailing list of five sibling tools is long but earns its place as routing guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the description covers what is returned (current chapter, current sub-phase, dates, what comes next and when, ordering) as well as auth prerequisites and alternatives. An agent has everything needed to call it correctly.

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 100%, and both parameters (lang enum, profile name-or-id with omit-for-all semantics) are fully documented in the schema. The description only restates the 'one person or everyone' behavior the schema already encodes, adding no format or edge-case detail.

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?

Names a specific resource (Mahadasha/Antardasha life phases) and scope (one saved person or the whole account), plus the output ordering. It clearly separates itself from explain_dasha and life_timeline, which it explicitly names as the typed-birth-details path.

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 concrete trigger situations ('why life feels stuck', 'when things will change', 'timing for family members') and an explicit exclusion: it only covers people saved on the account, with typed birth details routed to free_kundli, kundli_milan, explain_dasha, full_chart and life_timeline.

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

All AstroCalc: 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?