Skip to main content
Glama
nmhaaa3218

Tu Vi Horoscope MCP Server

by nmhaaa3218
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_saved_horoscope

Retrieve a saved horoscope profile and generate its full astrological chart using the stored birth data.

Instructions

Load a saved horoscope profile from the database and generate its astrological chart.

Purpose and Comparison

Use this tool to view or analyze a profile that has been previously saved using save_horoscope.

  • Contrast with generate_horoscope: Use get_saved_horoscope to avoid re-entering full birth parameters for recurring profiles. Use generate_horoscope for raw inputs not saved in the database.

  • Contrast with list_saved_horoscopes: Use list_saved_horoscopes to inspect what records exist. Use get_saved_horoscope to actually load the record and compute its full chart.

  • Contrast with delete_saved_horoscope: Use delete_saved_horoscope to permanently remove records.

Side Effects, Auth, and Rate Limits

  • Side Effects: Read-only database retrieval and in-memory chart calculations. No database writes or file writes.

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

Prerequisites

  • The target horoscope record must exist in the SQLite database.

  • To check existing records, first run list_saved_horoscopes.

Parameter Guidelines & Interactions

  • At least one of horoscope_id or name must be provided.

  • horoscope_id: The unique integer ID of the saved database record.

  • name: The name of the saved person.

  • Interactions & Precedence: If both parameters are supplied, horoscope_id takes precedence. If only name is provided and multiple records match, the latest saved record for that name is retrieved.

Output Schema and Error Conditions

  • Returns: A dictionary containing the full astrological chart structure (chart_data) with an added "metadata" section:

    • thien_ban: Demographic, pillars/Can-Chi, and basic zodiac metadata.

    • dia_ban: List of 12 houses (cung), each containing names, elements, stars, and transit info.

    • metadata: A dictionary with keys {"id": <int>, "notes": <str>, "created_at": <timestamp>} containing database record details.

  • Errors:

    • Returns {"error": "Horoscope record not found"} if no matching record exists in the database for the given ID or name.

    • Returns {"error": "error_message"} if database access fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
horoscope_idNo

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description fully covers side effects ('Read-only database retrieval and in-memory chart calculations, no writes'), auth/rate limits ('runs locally, no auth or external limits'), and error conditions. This is thorough and honest.

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 bullet points, but it is quite long. Every section adds value, so it earns a 4 rather than 5.

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 output schema and moderate complexity (astrological chart), the description covers return format (chart_data with metadata), error conditions, prerequisites, and side effects comprehensively. Leaves no gaps.

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 coverage is 0%, but the description explains both parameters in detail: at least one required, precedence rules (horoscope_id takes precedence), and behavior when name matches multiple records (latest retrieved). Adds significant value beyond the schema.

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 'Load a saved horoscope profile from the database and generate its astrological chart.' It uses a specific verb+resource and distinguishes itself from siblings in the 'Purpose and Comparison' section.

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 contrasts with three sibling tools (generate_horoscope, list_saved_horoscopes, delete_saved_horoscope) with clear when-to-use and when-not-to-use guidance. Also mentions prerequisites and recommends running list_saved_horoscopes first.

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