Skip to main content
Glama
adityarya24

Astro Skill MCP Server

by adityarya24

Generate PDF Report

generate_pdf_report

Render a client-facing PDF report including Lagna/Navamsa charts, planet table, and dasha timeline from a kundali. Supports optional sections like panchang and transit, written to disk.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandNoOptional white-label footer text. Empty keeps the report's neutral footer.
dashaNoOptional dasha JSON from calculate_dasha; adds the dasha timeline section.
gocharNoOptional gochar JSON from calculate_gochar; adds the transit section.
db_pathNoSQLite store to record the report in; when omitted the report is only written to disk. Must resolve inside the server working directory, the system temp directory, or ASTRO_MCP_BASE_DIR; other paths are rejected.
kundaliYesKundali JSON exactly as returned by the calculate_kundali tool.
languageNoReport language: 'hin' or 'hi' for Hindi (Devanagari), 'en' for English.hin
panchangNoOptional panchang JSON from calculate_panchang; adds the panchang section.
rendererNoPDF rendering backend. Only the pure-Python ReportLab renderer is supported.reportlab
templateNoPDF layout. Only the standard factual report template is supported.standard
client_idNoClient identifier the report is filed under.anonymous
output_dirNoDirectory the report file is written into (default: data/reports). Must resolve inside the server working directory, the system temp directory, or ASTRO_MCP_BASE_DIR; other paths are rejected.
client_nameNoClient/native name shown on the PDF cover page
Behavior4/5

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

The description discloses the action (writes PDF to disk, optionally records in SQLite) and the return value. Annotations show no destructive or read-only hints, and the description does not contradict them. However, it does not mention potential side effects like overwriting files or required permissions.

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 description is a single sentence that front-loads the tool's purpose and key output. It is concise, but could be better structured to separate required and optional parts.

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

Completeness3/5

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

Given the tool's complexity (12 parameters, nested objects, no output schema), the description is relatively brief. It mentions the return value but lacks detail on error conditions, prerequisites beyond having a kundali, or the behavior of the optional sections.

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?

The input schema has 100% description coverage for all parameters. The tool description adds context about the overall flow and mentions the renderer, but it does not significantly enhance understanding of individual parameters beyond the schema descriptions.

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?

The description states a specific action (render a PDF report), lists key sections (cover, charts, planet table, dasha timeline), and identifies the input (kundali) and optional additions. It clearly distinguishes from sibling tools which perform calculations or data management.

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?

The description implicitly indicates when to use this tool (to generate a PDF from a kundali) and mentions optional sections from other tools (dasha, gochar, panchang). However, it does not explicitly state when not to use it or provide alternatives beyond the implied prerequisite calculations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adityarya24/astro-skill'

If you have feedback or need assistance with the MCP directory API, please join our Discord server