Skip to main content
Glama
astroway

astroway-mcp

Official

Yogas — Pancha Mahapurusha (5 great)

vedic_yogas_parashara_pancha_mahapurusha
Read-onlyIdempotent

Calculate the five Pancha Mahapurusha Yogas in Vedic astrology: Ruchaka, Bhadra, Hamsa, Malavya, and Sasha. Determines if each planet is in its own or exalted sign and in a kendra house.

Instructions

5 Mahapurusha yogas: Ruchaka (Mars), Bhadra (Mercury), Hamsa (Jupiter), Malavya (Venus), Sasha (Saturn). Each formed when respective planet is in its own/exalted sign AND in a kendra (1/4/7/10).

[Group: Vedic] [Cost: 50 credits (Tier 3)]

Example request body: {"date":"1990-05-15","time":"14:30:00","timezoneOffset":3,"latitude":50.45,"longitude":30.52}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
timeYes
timezoneOffsetNo
latitudeNo
longitudeNo
houseSystemNoP
nameNo
cityNo
zodiacTypeNo
ayanamsaIdNo
cosmogramNo
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds cost (50 credits) and group (Vedic), but no behavioral traits beyond what annotations provide. No contradictions.

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 short and mostly relevant, but includes redundant listing of yogas with planets (already covered in the list). Front-loads purpose well. Group and cost info are useful extras.

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

Completeness2/5

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

No output schema, no description of return values or behavior for this complex astrological calculation. Many parameters remain unexplained. Incomplete for an agent to use correctly without external knowledge.

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

Parameters1/5

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

Input schema has 11 parameters with 0% description coverage. The description only shows an example request body for date/time/location. Other parameters like houseSystem, zodiacType, ayanamsaId, cosmogram are not explained, leaving the agent without necessary context.

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 clearly states the tool computes the 5 Mahapurusha yogas, listing each by name and associated planet (Ruchaka-Mars, etc.) and defines the formation condition (planet in own/exalted sign AND in kendra). This is specific and distinguishes it from generic yoga tools.

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?

No guidance on when to use this tool vs alternatives like vedic_yogas_parashara_dhana or vedic_yogas_jaimini_full. The description does not provide usage context or exclusions.

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/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server