Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Yogas: Jaimini Dhana yoga

astroway_vedic_yogas_jaimini_dhana
Read-onlyIdempotent

Identify Jaimini Dhana yoga and assess wealth indicators by checking if AK or AmK sits in the 2nd or 11th house from lagna using birth date, time, and location.

Instructions

Jaimini Dhana yoga: AK or AmK in 2nd / 11th from lagna. Wealth indicator.

[Group: Vedic] [Endpoint: POST /v1/vedic/yogas/jaimini/dhana] [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_jaimini_dhana"
  }
}

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
lagnaSignNo
atmakarakaNo
amatyakarakaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so safety is covered. The description adds a genuinely useful non-schema fact - 20 credits at Tier 2 - which matters for cost-conscious planning, but says nothing about what the response contains or how the yoga evaluation is derived.

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 defining rule and its interpretation are front-loaded in one line, and the bracketed metadata blocks are compact and scannable. The cost/endpoint tags are boilerplate but each carries a fact the agent may need, so little is wasted.

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?

For a 13-parameter Vedic calculation with an output schema present, the description omits any mention of the sidereal/ayanamsa settings that dominate those extra parameters, and gives no hint of what the yoga result looks like. It is adequate only for the absolute minimum of supplying birth data.

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?

With 13 parameters at 23% schema description coverage, the description carries most of the burden, yet it only restates the four required fields that the schema's required array already lists. It says nothing about the optional ayanamsa, zodiacType, houseSystem, or cosmogram choices, which materially change a Jaimini sidereal calculation.

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?

It names the specific technique (Jaimini Dhana yoga) and gives the defining condition (AK or AmK in the 2nd/11th from lagna), which lets an agent separate it from siblings like astroway_vedic_yogas_parashara_dhana or astroway_vedic_yogas_jaimini_raja. The only weakness is the absence of an explicit verb - 'Wealth indicator' implies the output is a wealth assessment rather than spelling out that it detects/evaluates the yoga.

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 statement of when to pick this over the many adjacent tools (parashara_dhana, jaimini_full, financial_wealth_house, jaimini_yogas). The agent must infer eligibility purely from the yoga definition; no prerequisites, exclusions, or alternative routing are given.

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