save_horoscope
Store birth chart data in a local SQLite database for future access. Retrieve saved horoscopes by name or ID without re-entering details.
Instructions
Save birth chart details to the local SQLite database for future retrieval.
Purpose and Comparison
Use this tool to save a horoscope profile so it can be re-accessed later via ID or Name without entering birth details again.
Contrast with
generate_horoscope: Usesave_horoscopewhen you want to save details permanently. Usegenerate_horoscopeif you only want to compute/view a chart on-the-fly without database persistence.After saving, you can retrieve the chart using
get_saved_horoscope.
Side Effects, Auth, and Rate Limits
Side Effects: Modifies persistent state by inserting a new record into the local SQLite database (
~/.tuvi_mcp/tuvi_horoscopes.db).Auth/Rate Limits: Runs entirely locally. No authentication or external rate limits apply.
Prerequisites
Local SQLite database must be writable.
Parameter Guidelines & Interactions
name: Name of the person (required, text).day: Day of birth (1-31).month: Month of birth (1-12).year: Year of birth (four-digit year).hour_val: Hour of birth (e.g., "14:30", "Ngọ" or index 1-12).gender_val: Gender ("Nam" or "Nữ").is_solar: Set toTrue(default) if birth date is Solar,Falseif Lunar.notes: Optional textual comments or notes.
Output Schema and Error Conditions
Returns: A success dictionary containing:
message: Success confirmation string.id: The unique integer ID of the newly created database record.
Errors: Returns
{"error": "error_message"}if birth details are invalid or database write fails.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| day | Yes | ||
| name | Yes | ||
| year | Yes | ||
| month | Yes | ||
| notes | No | ||
| hour_val | Yes | ||
| is_solar | No | ||
| gender_val | Yes |