Skip to main content
Glama
nmhaaa3218

Tu Vi Horoscope MCP Server

list_saved_horoscopes

Retrieve all locally saved horoscope profiles to find database IDs or names before loading or deleting records.

Instructions

Retrieve all saved horoscope profiles from the local database.

Purpose and Comparison

Use this tool to discover previously saved horoscope records, allowing you to find their database IDs or names before loading them with get_saved_horoscope or removing them with delete_saved_horoscope.

Side Effects, Auth, and Rate Limits

  • Side Effects: Read-only database query. No state modifications or file writes.

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

Prerequisites

  • Local SQLite database must exist and be readable.

Output Schema and Error Conditions

  • Returns: A list of dictionaries, where each dictionary represents a saved horoscope profile with the keys:

    • id: The unique integer record ID.

    • name: Name of the person.

    • day: Day of birth.

    • month: Month of birth.

    • year: Year of birth.

    • hour: Saved hour (as a branch index 1-12).

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

    • is_solar: Boolean (True if Solar, False if Lunar).

    • notes: Optional comment string.

    • created_at: The database insertion timestamp.

  • Errors: Returns a list containing an error dictionary [{"error": "error_message"}] if database query fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. It clearly states 'Read-only database query. No state modifications or file writes.' and addresses auth/rate limits as local only. However, it could be more comprehensive about concurrent access behavior.

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?

Description is well-structured with headings and bullet points, front-loading the purpose. While somewhat lengthy, every section adds value (usage, side effects, output). Could be slightly more concise but is appropriate for the detail provided.

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?

No output schema exists, but description thoroughly details the return format (list of dicts with all keys), error conditions, side effects, auth, and prerequisites. Highly complete for a list tool with no parameters.

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?

Tool has no parameters (0 params, schema coverage 100%). Per guidelines, baseline is 4. Description adds no param info because none exist, but provides output schema details which are not penalized.

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?

Description clearly states 'Retrieve all saved horoscope profiles from the local database.' It explicitly distinguishes from siblings like get_saved_horoscope and delete_saved_horoscope by explaining its role in discovering IDs and names before those actions.

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?

The 'Purpose and Comparison' section explicitly says when to use this tool and contrasts it with get_saved_horoscope and delete_saved_horoscope. It also includes prerequisites about database existence.

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