Astro Skill MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_birth_detailsA | Conservatively extract dob, tob, place, lat, lon, and timezone from a short operator note. Returns the recognised fields plus a 'missing' list naming everything that could not be parsed, so the agent can ask the operator for clarification instead of guessing. |
| calculate_kundaliA | Compute a sidereal Vedic kundali (birth chart) from birth details: lagna, Moon rashi, nakshatra with pada, planet positions with sign and whole-sign house placements, navamsa (D9) and further divisional charts, ashtakavarga tables, and the Vimshottari dasha seed. Returns the kundali JSON that the dasha, gochar, compatibility, and report tools consume. |
| calculate_dashaA | Compute the Vimshottari dasha timeline from a kundali: mahadasha and antardasha periods with start/end dates, plus the running mahadasha/antardasha/pratyantardasha for on_date. Returns dasha JSON accepted by the report tools. |
| calculate_gocharA | Compute gochar — planetary transits relative to the natal Moon and Lagna — plus the Saturn Sade Sati / Dhaiya phase for a date. Returns gochar JSON accepted by the report tools. |
| calculate_compatibilityA | Guna Milan (Ashtakoot, 36-point) marriage compatibility between two kundali JSONs (kundali_a = bride, kundali_b = groom). Returns the koota-wise point breakdown, the total out of 36, and Nadi, Bhakoot, and Manglik dosha findings. |
| calculate_panchangA | Compute the daily Panchang for a place and date: vara, tithi, nakshatra, yoga, karana, and sunrise/sunset times. Returns panchang JSON accepted by the report tools. |
| generate_report_jsonA | Assemble a structured astrology report draft (birth chart summary plus optional dasha/panchang/gochar sections) and write it to disk as JSON. Returns the report record: report_id, path of the written file, client_id, and created_at. |
| generate_pdf_reportA | Render a client-facing PDF report (cover, Lagna/Navamsa charts, planet table, dasha timeline) from a kundali plus optional sections, using the in-process ReportLab renderer. Returns the report record with the path of the written PDF. |
| save_client_profileA | Create or update (upsert by client_id) a client profile in the SQLite store, optionally with birth details. Returns the saved profile. |
| find_client_profileA | Look up a client profile by exact client_id, otherwise by case-insensitive display_name substring. Returns the profile, or null when nothing matches. |
| list_client_reportsB | List report records previously generated for a client, newest first. Each record carries report_id, report_type, path, and created_at. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools target distinct astrological calculations or client operations, making selection clear. The only mild overlap is generate_report_json vs generate_pdf_report, which both assemble reports but differ in output format, so an agent must rely on descriptions to choose.
All 11 tools use snake_case with a predictable verb_noun structure (calculate_*, list_*, parse_*, generate_*, find_*, save_*). No naming inconsistencies or mixed conventions are present.
11 tools fit the domain well: five calculation types, birth parsing, two client profile operations, two report generators, and report listing. No tool feels redundant or missing at this scale.
Core lifecycle for astrology calculations and reports is covered, including parsing, calculation, report generation, and client profile upsert/lookup. Minor gaps exist (e.g., no delete for profiles/reports, no list_clients), but agents can work around them.