Birthstar Vedic Astrology MCP

get_aspects

Get planetary and sign aspects — who is looking at which house.

Graha drishti is the Parasari planetary aspect (everything aspects the 7th;
Mars, Jupiter, Saturn and the nodes have special aspects). Rasi drishti is
the Jaimini sign aspect, a different system — do not merge the two.

Args:
    chart_id: Handle returned by create_chart.
    planet: Restrict graha drishti to one graha.
    include_argala: Add Argala and Virodhargala (Jaimini intervention).
        Off by default — it roughly doubles the response.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`planet`	No
`chart_id`	Yes
`include_argala`	No

Schema Changelog

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

First observedSep 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it explains that graha and rasi drishti are separate systems, discloses that include_argala is off by default and 'roughly doubles the response,' and clarifies that planet restricts only graha drishti. This goes beyond the schema and gives useful behavioral warnings, though it does not describe response structure or error behavior.

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 concise and well-structured: a one-line summary, a short explanatory paragraph about the two systems, and a clean Args list. Every sentence contributes to understanding or usage, and the critical 'do not merge' warning is front-loaded in the explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 3 parameters, no output schema, and no annotations, the description provides a solid conceptual model plus parameter-level guidance. The main gap is that it never explicitly states that both graha and rasi drishti are returned together in the response, but the overall content is sufficient for an agent to call the tool correctly in most cases.

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?

Although schema description coverage is 0%, the description's Args section fully documents all three parameters. chart_id is tied to create_chart, planet is scoped to graha drishti, and include_argala includes its default and performance impact. This more than compensates for the missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'Get planetary and sign aspects — who is looking at which house.' It clearly identifies the tool's domain as aspects and distinguishes between graha drishti and rasi drishti. However, it does not explicitly name or contrast sibling tools like get_grahas or get_houses, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on the two aspect systems and warns 'do not merge the two,' which is a direct usage instruction. It also explains when the planet parameter applies (only to graha drishti) and when include_argala is relevant. It does not mention alternative tools or explicit when-not-to-use scenarios, but the guidance given is substantive.

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?