Birthstar Vedic Astrology MCP

get_prompt_library

Fetch curated high-value prompt templates and multi-tool question workflows.

Call this tool whenever you want to suggest high-value questions to the user,
or when the user asks "what can you do?", "what should I ask?", or wants
guided astrology workflows (e.g. Sade Sati analysis, timeline forecast,
dasha transitions, chart strength, school comparisons, timing windows).

Args:
    category: Optional category filter. One of 'all', 'Core Reading',
        'Timing & Transits', 'Career & Wealth', 'Strengths & Accuracy',
        'Relationships', 'Daily & Remedies'. Names are matched
        case-insensitively; an unrecognised one is an error listing the
        valid names, never a silent empty result.
    include_full_templates: Set to True to retrieve the full expanded prompt text.
        Defaults to False for compact workflow titles and tool chains.

Returns a structured catalog of prompt templates with their titles, descriptions,
required arguments, and which underlying tools they chain.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`category`	No
`include_full_templates`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 5, 2026

TDQS

A5/5.0

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 it delivers: it explains category matching is case-insensitive, unrecognized categories produce an error listing valid names rather than a silent empty result, and include_full_templates defaults to False with a clear effect on output. It also describes the general return structure.

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?

The description is front-loaded with the core purpose, followed by concrete trigger examples, then parameter details, and finally return-value expectations. Every sentence adds useful information; there is no filler or redundancy.

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 there is no output schema and no annotations, the description is exceptionally complete: it states the output is a structured catalog with titles, descriptions, required arguments, and underlying tool chains. It also covers error behavior and defaults, so an agent has enough context to select and invoke the tool confidently.

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 fully compensates by enumerating the valid category values, explaining the default behavior, and defining exactly what include_full_templates does. An agent can populate both parameters correctly without any external documentation.

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 and resource: 'Fetch curated high-value prompt templates and multi-tool question workflows.' It also clearly distinguishes this tool from the sibling astrology data tools, as it targets user-facing question guidance rather than chart calculations.

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?

It explicitly states when to call the tool: when suggesting high-value questions, when the user asks 'what can you do?' or 'what should I ask?', and for guided astrology workflows such as Sade Sati analysis. This is strong practical guidance that an agent can act on immediately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Birthstar Vedic Astrology MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Every tool targets a distinct astrological subsystem — positions, houses, aspects, strengths, dashas, transits, yogas, doshas, vargas, karakas, etc. The pairs that could plausibly be confused (calculate_birth_star vs create_chart, get_current_dasha vs get_dasha_periods, get_timeline vs get_transits) are explicitly cross-referenced with guidance on when to use which, so an agent can disambiguate reliably.

Naming Consistency4/5

24 of 30 tools follow a uniform get_X pattern, and the remaining action tools (create_chart, calculate_birth_star, describe_chart, rectify_birth_time) still use verb_noun. Only health_check and server_stats break the pattern as noun-style names, and the different verbs reflect genuinely different actions rather than inconsistency.

Tool Count3/5

30 tools is on the heavy side and exceeds the comfortable range, even though Vedic astrology is a genuinely broad domain with many distinct subsystems. Some tools are meta or adjacent (get_account_status, health_check, server_stats, get_prompt_library, get_numerology) and a couple could arguably be consolidated (get_current_dasha as a mode of get_dasha_periods), but each tool does carve out a distinct purpose.

Completeness5/5

The chart lifecycle is fully covered: create_chart produces a cached handle, describe_chart inventories it, and the get_* readers retrieve every section. Timing (dashas, transits, timeline), strengths (shadbala, vimsopaka), yogas, doshas, vargas, compatibility, rectification, and even meta-concerns (account status, health) are all present with no obvious dead ends or missing operations for a computation-cache domain.

Resources

Need Help?