Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Yogas: Parashara full report

astroway_vedic_yogas_parashara_full
Read-onlyIdempotent

Generate a combined Parashara yoga report by running six detectors—Raja, Dhana, Dharma-Karmadhipati, Pancha-Mahapurusha, Gajakesari, and Adhi—from birth date, time, and coordinates.

Instructions

Combined Parashara yoga report: runs all 6 detectors (Raja/Dhana/Dharma-Karmadhipati/Pancha-Mahapurusha/Gajakesari/Adhi) and returns one structured response.

[Group: Vedic] [Endpoint: POST /v1/vedic/yogas/parashara/full] [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_full"
  }
}

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
adhiNo
rajaNo
dhanaNo
schoolNo
lagnaSignNo
gajakesariNo
panchaMahapurushaNo
dharmaKarmadhipatiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely non-structured context: the exact endpoint (POST /v1/vedic/yogas/parashara/full), the required input set, and a per-call cost of 20 credits (Tier 2), which is a real behavioral trait an agent must weigh. It also notes the output is 'one structured response', clarifying that six detectors are batched rather than returned separately.

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 core sentence is front-loaded and waste-free: it names the tool's function and its six components in one line. The bracketed metadata block is structured and scannable rather than prose bloat, though the 'Required' line is redundant with the schema's required array.

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?

The existence of an output schema relieves the description of explaining return values, and the aggregation scope is fully stated. However, for a 13-parameter Vedic computation with only 23% schema coverage and three enums, the description says nothing about how ayanamsa/houseSystem/zodiacType choices affect results or what to do when timezone is ambiguous — gaps that matter more here than for a simple lookup.

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% across 13 parameters, so the description must carry meaning — and it does not. The '[Required: date, time, latitude, longitude]' line merely restates the schema's required array, and there is no explanation of high-impact optional parameters such as ayanamsa (with its 10-value enum), zodiacType, houseSystem, or the timezone vs timezoneOffset precedence, all of which materially change Vedic results.

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?

States a specific verb and resource ('Combined Parashara yoga report') and enumerates exactly what it aggregates: all six detectors (Raja/Dhana/Dharma-Karmadhipati/Pancha-Mahapurusha/Gajakesari/Adhi). Because those six names map directly to sibling tools (astroway_vedic_yogas_parashara_raja, _dhana, etc.), an agent can distinguish this aggregate from the single-yoga tools without opening any schema.

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?

Usage is only implied: the word 'Combined' plus 'runs all 6 detectors' signals this is the bulk option and that the individual parashara_* detectors are the narrow alternatives, but the description never says 'use this instead of X when Y' or when to prefer the single-detector calls. The 'Cost: 20 credits (Tier 2)' line gives an implicit cost trade-off cue but no explicit decision rule against the cheaper single-yoga siblings or astroway_vedic_yogas_jaimini_full.

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