Skip to main content
Glama

Yogas: Surya (Vesi, Vasi, Ubhayachari)

astroway_vedic_yogas_parashara_surya
Read-onlyIdempotent

Yogas counted from the Sun, BPHS 38.1: Vesi (a planet from Mars onwards, not the Moon, in the 2nd from the Sun), Vasi (12th), Ubhayachari (both). Rahu and Ketu are not counted. The yoga and the planets that form it; no result text.

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

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
vasiNo
vesiNo
yogaNo
schoolNo
sourcesNo
sunSignNo
lagnaSignNo
ubhayachariNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral facts: a 20-credit Tier 2 cost, the endpoint, and the important caveat that it returns no result/interpretation text. What it does not disclose is whether ayanamsa/house-system choices alter the yoga count.

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 technical definition is front-loaded and tight, and the bracketed metadata block is scannable. The definitional parenthetical is slightly dense but every clause carries information; nothing is padded.

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 omitting return-value detail is acceptable, and the 'no result text' note usefully pre-empts an expectation of interpretation. However, for a 15-parameter sidereal calculation, leaving ayanamsa and house-system selection unexplained is a real gap an agent would have to guess around.

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 33% across 15 parameters, so the description would need to compensate. Instead it merely repeats the four required fields already declared in the schema's required array and says nothing about ayanamsa, zodiacType, houseSystem, ayanamsaId, cosmogram, city/name, or how `fields`/`precision` interact with this yoga-only response.

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 defines the three yogas concretely (Vesi = planet from Mars onward in the 2nd from the Sun, Vasi = 12th, Ubhayachari = both) and states the return payload ('the yoga and the planets that form it'). The phrase 'counted from the Sun' implicitly separates it from the Moon-based sibling astroway_vedic_yogas_parashara_chandra, though no sibling is named explicitly.

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 via the BPHS citation and the Sun-based framing; there is no statement of when to call this versus astroway_vedic_yogas_parashara_full or the chandra variant. No prerequisites are given beyond the required date/time/lat/long list.

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