Skip to main content
Glama
nmhaaa3218

Tu Vi Horoscope MCP Server

get_van_han

Calculate transit stars and active houses (Đại Hạn, Tiểu Hạn, Nguyệt Hạn) for a specified Lunar year and month to analyze luck and predictions.

Instructions

Calculate transit stars (sao lưu) and active houses (Đại Hạn, Tiểu Hạn, Nguyệt Hạn) for the target Lunar period.

Purpose and Comparison

Use this tool to perform transit/vận hạn luck analysis (inspecting star shifts, Đại Hạn, Tiểu Hạn, and monthly Nguyệt Hạn transits) for a specific target Lunar year and month.

  • Contrast with generate_horoscope: Use get_van_han specifically for inspecting luck/predictions during a specific target timeframe. Use generate_horoscope to get the static, base birth chart.

Side Effects, Auth, and Rate Limits

  • Side Effects: None. This is a read-only calculation and does not write to the database or render filesystem files.

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

Prerequisites & Calendar Conversions

  • CRITICAL: The parameters current_year and current_month represent the Lunar year and Lunar month. If the user asks to inspect a specific Solar period (e.g., 'October 2026' or 'May 15th, 2026'), you MUST first use the convert_calendar tool to find the corresponding Lunar month/year before calling this tool.

Parameter Guidelines & Interactions

  • name: Name of the person.

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

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

  • year: Year of birth.

  • hour_val: Hour of birth (e.g., "14:30", "Ngọ").

  • gender_val: Gender ("Nam" or "Nữ").

  • is_solar: True if birth date is Solar (Dương lịch), False if Lunar (Âm lịch).

  • current_year: Target Lunar year to inspect (defaults to current system year, e.g., 2026).

  • current_month: Target Lunar month to inspect (1-12, default 1).

Output Schema and Error Conditions

  • Returns: A dictionary containing:

    • person_details: Summary of demographic details (name, lunar birth date, etc.).

    • target_period: Contains current_year, current_year_can_chi, current_month_lunar, and current_age representing the target period parameters.

    • transit_stars: List of transit stars (e.g. Lưu Thái Tuế, Lưu Lộc Tồn) and their current coordinates/cung indexes.

    • dai_han: Details of the active 10-year major cycle house.

    • tieu_han: Details of the active 1-year minor cycle house.

  • Errors: Returns an error dictionary {"error": "error_message"} if birth details are invalid or calculation fails.

Input Schema

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

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

Since no annotations are provided, the description carries full burden. It explicitly states side effects are none (read-only calculation), no auth or rate limits, runs locally, and includes error conditions. This fully discloses behavioral traits.

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 well-structured with clear sections and front-loaded purpose. While some redundancy exists (e.g., repeating 'transit stars' in multiple sections), overall it is organized and each section adds value.

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 the tool's complexity (9 parameters, no output schema, no annotations), the description is remarkably complete. It covers prerequisites, parameter guidelines, output dictionary structure, error handling, and behavioral aspects, leaving little ambiguity for the agent.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It lists each parameter with a brief explanation, including the critical distinction that current_year and current_month are Lunar and require prior conversion. However, descriptions are minimal and could provide more detail on formats or constraints.

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 clearly states the tool's purpose: 'Calculate transit stars and active houses for the target Lunar period.' It distinguishes from sibling tool generate_horoscope by specifying that this tool is for transit analysis, not static chart generation.

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?

Explicitly states when to use this tool: for transit/vận hạn luck analysis during a specific target timeframe. It contrasts with generate_horoscope and provides a critical prerequisite: must use convert_calendar if user provides a Solar date.

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