Skip to main content
Glama

caelus-mcp

by io.github.heavyblotto

nakshatras

The nakshatra (one of the 27 lunar mansions of 13°20′) of each classical point on the sidereal zodiac: the seven traditional planets and the Ascendant (lagna). Per point: the nakshatra name, its pada (quarter, 1–4), the ruling planet (the Vimshottari lord), and degrees into the nakshatra. The Moon's nakshatra (janma nakshatra) anchors the Vimshottari dasha. Sidereal by definition; Lahiri ayanamsa by default. Needs the birth time and place for the Ascendant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude, north positive
lonYesLongitude, EAST positive (Americas are negative)
dateYesUTC date-time, ISO 8601, e.g. 1990-06-10T14:30:00Z. Convert local birth time to UTC first.
zodiacNosidereal ayanamsa (default sidereal:lahiri); these are sidereal techniquessidereal:lahiri

TDQS

A4.1/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that the tool is sidereal by default, specifies default ayanamsa (Lahiri), and notes that birth time and place are needed for Ascendant. Covers key behavioral traits clearly.

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?

Single paragraph, information-dense but well-organized. Every sentence adds value. Could be slightly more structured but is appropriately sized.

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?

No output schema, but description adequately explains what the tool returns (per-point nakshatra details). Mentions the classical points considered. Does not specify exact output format but provides sufficient context for an AI agent to invoke correctly.

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?

Schema description coverage is 100%, so baseline is 3. Description adds value by explaining the 'date' parameter as needing UTC conversion and confirming that birth time/place are required for Ascendant. Reinforces default ayanamsa choice.

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 explicitly states it returns nakshatra info (name, pada, ruling planet, degrees) for each classical point (7 planets + Ascendant). Clearly distinguishes from sibling tools like 'dasha' by explaining the connection to Vimshottari dasha.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance. However, the description makes clear it is for computing nakshatra positions, which implies usage context. Does not name alternatives.

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

All caelus-mcp toolsInspect
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

A3.9/5.0
Disambiguation5/5

Each tool has a highly specific and well-described purpose. Despite the large number, their functions are clearly distinct—e.g., natal_chart vs current_sky vs composite, or dasha vs firdaria vs profections vs releasing. The detailed descriptions prevent ambiguity.

Naming Consistency3/5

Names are consistently in snake_case but vary in style: some are noun phrases (natal_chart, cosmic_weather), some are verb-like (releasing, returns), and some are descriptive (aspect_patterns, find_aspect_dates). There is no strict verb_noun pattern, leading to moderate consistency.

Tool Count4/5

34 tools is high but appropriate for a comprehensive astrology API covering natal, transits, progressions, returns, synastry, time-lord techniques, sky events, and synthetic bodies. Each tool serves a specific niche, so the count feels justified rather than excessive.

Completeness5/5

The tool surface is extremely thorough, covering all major areas of astrology: chart generation, aspects, configurations, dignities, time-lord techniques (multiple systems), synastry, composite, progressions, returns, transits, sky events, rectification, electional, and synthetic bodies. No obvious gaps for the intended domain.

Resources