Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Yogas: Adhi

astroway_vedic_yogas_parashara_adhi
Read-onlyIdempotent

Detects Adhi Yoga and Maha Adhi Yoga in a Vedic birth chart by checking whether Mercury, Venus, and Jupiter occupy the 6th, 7th, or 8th houses from the Moon.

Instructions

Adhi Yoga: benefics (Mercury, Venus, Jupiter) in 6th, 7th, 8th houses from Moon. Maha Adhi Yoga when all three benefics are positioned там. Powerful for status and prosperity.

[Group: Vedic] [Endpoint: POST /v1/vedic/yogas/parashara/adhi] [Required: date, time, latitude, longitude] [Cost: 20 credits (Tier 2)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "time": "<time>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_vedic_yogas_parashara_adhi"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
cosmogramNo
longitudeYes
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
yogaNo
schoolNo
detailsNo
presentNo
strengthNo
lagnaSignNo
contributingPlanetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, and the description still adds information the annotations and schema do not carry: the 20-credit Tier 2 cost, the POST endpoint, and the four mandatory inputs. The one gap is that the definitional sentence is garbled ('positioned там' — presumably 'in all three'), so the exact Maha Adhi condition stays vague.

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 substantive definition comes first in two tight sentences, followed by a compact, consistently formatted metadata block; nothing is duplicated. Points off for the stray non-English token ('там') and the truncated Maha Adhi clause, which waste a slot that should carry the missing condition.

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

Completeness3/5

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

An output schema exists, so return values needn't be explained, and the safety profile is covered by annotations. What remains missing is meaningful treatment of the nine optional chart-configuration parameters and a legible statement of the Maha Adhi condition, both of which an agent needs to call this correctly rather than by guesswork.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 23%, so the description should compensate, but it only restates the four required parameters (date, time, latitude, longitude) that the schema already marks required. The nine optional parameters — ayanamsa/ayanamsaId, zodiacType, houseSystem, timezone vs timezoneOffset, cosmogram — are never mentioned, leaving the agent to discover the sidereal/ayanamsa choices on its own.

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 states concretely what is detected — benefics Mercury, Venus and Jupiter occupying the 6th/7th/8th from the Moon, with a Maha Adhi variant — so an agent knows this computes one specific Vedic yoga rather than a general chart. Sibling yoga tools (gajakesari, raja, dhana, full) are implicitly separable by the named yoga, though the name alone is never contrasted with them.

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

Usage Guidelines2/5

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

There is no when-to-use/when-not guidance and no routing to alternatives such as astroway_vedic_yogas_parashara_full, which presumably also reports Adhi Yoga along with other yogas. The only selection cues are the bracketed '[Required: ...]' and '[Cost: 20 credits (Tier 2)]' tags, which are cost facts rather than usage guidance.

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

Deploy Server

Other Tools