Skip to main content
Glama

Ashtakavarga: Trikona and Ekadhipatya shodhana, pinda

astroway_vedic_ashtakavarga_shodhana
Read-onlyIdempotent

The seven Bhinna Ashtakavargas reduced: Trikona shodhana (BPHS 67.4-5: the least of each trine taken from all three, a trine with a zero left alone), then Ekadhipatya shodhana (68.2-6: the two signs of one lord, by occupancy and bindus; Cancer and Leo stand alone), each pair's rule in ekadhipatyaSteps. Then Rasi pinda, Graha pinda and Shodhya pinda with the 69.2-4 multipliers. Occupancy counts the seven grahas.

[Group: Vedic] [Endpoint: POST /v1/vedic/ashtakavarga/shodhana] [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_ashtakavarga_shodhana"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
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
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
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
methodNo
planetsNo
sourcesNo
lagnaSignNo
signOrderNo
planetSignsNo
occupiedSignsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds genuine behavioral detail beyond that: the zero-in-a-trine edge case, the Cancer/Leo exception in Ekadhipatya, and that per-pair rules surface in `ekadhipatyaSteps`. It says nothing about cost, failure modes, or what happens when occupancy inputs are missing.

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?

Three dense sentences with the trikona, ekadhipatya, and pinda stages in execution order, which is the right front-loading. Sanskrit terminology is unavoidable here, and no sentence is filler.

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 need no explanation, and the algorithm itself is well covered. But for a 15-parameter, 20-credit endpoint with thin schema coverage, the description omits required-input expectations, ayanamsa/zodiac relevance, and any routing from the related Ashtakavarga tools.

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 coverage is only 33% across 15 parameters, so the description carries a heavy burden and adds nothing about date, time, latitude, longitude, ayanamsa, or precision. Only the incidental statement that occupancy counts the seven grahas touches on input semantics indirectly.

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 names the specific computations: Trikona shodhana, Ekadhipatya shodhana, and the three pinda values, with BPHS citations. An agent can tell this produces reduced Ashtakavarga values rather than the raw vargas. It does not, however, name or distinguish itself from the sibling tools astroway_vedic_ashtakavarga and astroway_vedic_ashtakavarga_prastara.

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 explicit statement of when to use this tool versus astroway_vedic_ashtakavarga (raw bindus) or astroway_vedic_ashtakavarga_prastara, nor any note that an Ashtakavarga chart is a logical prerequisite. Usage is only inferable from the domain language.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources