Skip to main content
Glama
nmhaaa3218

Tu Vi Horoscope MCP Server

generate_horoscope

Generate a complete Tu Vi horoscope chart from birth details (date, time, gender) with optional visual PNG rendering for instant astrological analysis.

Instructions

Generate a full Tu Vi (Vietnamese horoscope) chart from raw birth details, with optional high-quality visual chart image rendering.

Purpose and Comparison

Use this tool when you want to compute and inspect an astrological birth chart from scratch for arbitrary birth details.

Side Effects, Auth, and Rate Limits

  • Side Effects: If generate_image is True, it renders a high-quality PNG chart layout and saves it to a temporary path on the local filesystem, returning the file path. It is read-only and stateless.

  • Auth/Rate Limits: Runs entirely locally. No authentication or external rate limits apply.

Prerequisites

  • The date parameters must form a valid date in either the Solar or Lunar calendar.

Parameter Guidelines & Interactions

  • name: Name of the subject (default: "Khách").

  • day: Day of birth (1-31).

  • month: Month of birth (1-12).

  • year: Year of birth (e.g., 1995).

  • hour_val: Hour of birth. Accepts string formats like "14:30", "Ngọ" (Earthly Branch name), or numeric branch index (1-12, where 1=Tý, 12=Hợi) (default: "12:00"). Interpreted as the LOCAL CIVIL TIME at the birthplace — do not convert to Vietnam time unless that is the intended civil-tz reference (see timezone below).

  • gender_val: Gender of the subject. Accepts "Nam", "Nữ", "male", "female" (case-insensitive, default: "Nam").

  • is_solar: Set to True (default) if the birth date is Solar (Dương lịch). Set to False if it is Lunar (Âm lịch).

  • current_year: Year to calculate transit stars/Vận Hạn for (default: system current year, e.g., 2026).

  • generate_image: Set to True (default) to render and return a visual PNG chart along with raw data. Set to False to return only raw data.

  • timezone: Numeric UTC offset for the civil timezone at the birthplace (default 7 for ICT/Vietnam). Accepts an integer (e.g. 7, -5) or an h:30 string (e.g. "7:30", "-5:30"). Other minutes values (e.g. "7:15") and out-of-range values are rejected. Only the boundary-rounding of astronomical events (lunar day, tiết-khí, Đông chí) is affected — the civil hour branch (chi giờ) is always derived from hour_val.

Output Schema and Error Conditions

  • If generate_image is True: Returns a list [Image, chart_data] where Image is a FastMCP Image object pointing to the generated PNG file on disk, and chart_data is a dictionary containing structured chart details (demographics, houses, stars).

  • If generate_image is False: Returns only the chart_data dictionary.

  • Structure of chart_data:

    • thien_ban: Dict containing calculated demographics, pillars/Can-Chi (year, month, day, hour), element (Hành Cục), destiny (Bản Mệnh), etc.

    • dia_ban: List of 12 dicts, each representing an astrological house (cung), including cung_so (1-12), cung_ten (name), cung_chu (domain), sao (list of stars), quan_he_hinh_hoc (static 100% geometric relationships: xung_chieu, tam_hop, nhi_hop, giap_cung), and optional transit/Hạn keys.

  • Errors: Returns an error dictionary {"error": "error_message"} if calculations fail (e.g. invalid date formats, out-of-range birth years, invalid timezone).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNo
nameNoKhách
yearNo
monthNo
hour_valNo12:00
is_solarNo
timezoneNo
gender_valNoNam
current_yearNo
generate_imageNo
Behavior5/5

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

With no annotations, the description carries the full burden and succeeds. It explicitly discloses side effects (image rendering to a temporary path, read-only/stateless), auth/rate limits (fully local, no authentication or rate limits), and error behavior (returns error dictionary). This is exceptionally transparent for a tool with no annotation support.

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?

Although long, the description is well-structured with clear headings (Purpose and Comparison, Side Effects, Auth/Rate Limits, Prerequisites, Parameter Guidelines, Output Schema). Every section adds necessary detail for a complex 10-parameter tool, without irrelevant fluff.

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?

Given no annotations, no output schema, and high complexity, the description is remarkably complete. It covers side effects, auth, prerequisites, all parameters, output structure (both image and non-image branches), and error conditions. The output schema section even details the chart_data structure, so the agent knows exactly what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates fully. It explains every parameter's meaning, accepted formats (e.g., hour_val as '14:30', 'Ngọ', or branch index; timezone as integer or h:30 string), defaults, and interactions (e.g., timezone only affects boundary rounding of astronomical events). This greatly exceeds the schema information.

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 opens with a specific verb+resource statement: 'Generate a full Tu Vi (Vietnamese horoscope) chart from raw birth details, with optional high-quality visual chart image rendering.' It distinguishes from siblings via the 'Purpose and Comparison' section that directs usage to compute and inspect a birth chart from scratch, which is clearly distinct from the sibling tools (get_van_han, get_auspicious_info, convert_calendar).

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?

Provides clear context: 'Use this tool when you want to compute and inspect an astrological birth chart from scratch for arbitrary birth details.' However, it doesn't explicitly name alternative sibling tools or state when not to use this tool, so it stops short of the explicit when/when-not/alternatives level. Prerequisites and parameter guidelines add further usage context.

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/nmhaaa3218/TuViMCP'

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