AstroCalc: Vedic astrology

Full birth chart in detail (degrees, divisional charts)

full_chart

Read-onlyIdempotent

The complete birth chart for a detailed reading: Lagna degree; for each planet its sign, degree, nakshatra and pada, nakshatra lord, house, dignity, retrograde status, aspected houses and conjunctions; the 12 houses with lords and occupants; and divisional charts (D9 Navamsa and D10 Dasamsa by default, or any of D2, D3, D4, D7, D9, D10, D12, D16, D20, D24, D27, D30, D40, D45, D60) with vargottama planets. From birth details (free, no sign-in) or for a person saved on the user's AstroCalc account (profile; that needs a free sign-in). Use when a question needs more than the free_kundli summary: a deeper look at career, marriage (7th house, D9), a specific planet or house. AstroCalc calculates; the assistant interprets. Read-only.

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": "full_chart"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Birth latitude in decimal degrees (north positive). Give together with lon.
`lon`	No	Birth longitude in decimal degrees (east positive). Give together with lat.
`date`	No	Date of birth, YYYY-MM-DD (Gregorian calendar).
`lang`	No	Language of the text fields: 'en' (English, default) or 'hi' (Hindi).
`time`	No	Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'); '6:45 am' / '9:10 PM' also work. Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate.
`place`	No	Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given.
`vargas`	No	Divisional charts to include. Default ["D9", "D10"].
`profile`	No	A saved kundli on the user's AstroCalc account: its name as listed by my_profiles (e.g. 'Mummy') or its id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 8, 2026

changedInput schema / properties / time / description

Previous value: -"Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."New value: +"Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'); '6:45 am' / '9:10 PM' also work. Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."

changedInput schema / properties / time / pattern

Previous value: -"^(([01]\\d|2[0-3]):[0-5]\\d|unknown)$"New value: +"^(([01]?\\d|2[0-3]):[0-5]\\d|(0?[1-9]|1[0-2]):[0-5]\\d ?[AaPp][Mm]|unknown)$"

AddedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the auth distinction (birth details free/no sign-in vs. profile requires a free sign-in) and the division of labor ("AstroCalc calculates; the assistant interprets"), which tells the agent not to expect interpretation in the response. It does not discuss rate limits or response size for a very large payload.

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 return payload, then input modes, then the when-to-use rule — a sensible order. The long enumeration of planetary fields and the 15 varga codes is dense but each item is substantive for a chart tool; no filler sentences. Slightly long as a single block, which makes it harder to scan.

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?

With no output schema and no required parameters, the description carries the full burden and does: it spells out the return structure field by field, the default vargas, the two input paths, and the 'unknown' birth-time caveat. An agent has everything needed to call this correctly and to set expectations about the response.

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 schema already documents every parameter including defaults, patterns and the 'unknown' time fallback. The description only adds naming context (D9 Navamsa, D10 Dasamsa, vargottama planets) and the profile-vs-birth-details pairing, which is marginal beyond what the schema provides. Baseline 3 applies.

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 resource (complete birth chart) and enumerates exactly what it returns: Lagna degree, per-planet sign/degree/nakshatra/pada/lord/house/dignity/retrograde/aspects/conjunctions, 12 houses with lords and occupants, and varga charts. It explicitly contrasts itself with the free_kundli summary, so an agent can distinguish it from siblings without opening a schema.

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

Usage Guidelines4/5

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

"Use when a question needs more than the free_kundli summary: a deeper look at career, marriage (7th house, D9), a specific planet or house" gives a clear selection rule against the named sibling, and it states the two input modes (birth details vs. saved profile) with their sign-in implications. It does not, however, address other chart-ish siblings such as my_kundli or life_timeline, so the routing picture is not fully closed.

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?