Skip to main content
Glama

AstroWay Astrology API (full catalogue)

Prashna: yes/no indicators

astroway_vedic_prashna_analysis
Read-onlyIdempotent

Prasna Tantra indicators for one category (relationship, career, travel, lost-item, litigation, general; health is refused): the house of the question and its lord, the ascendant, the Lagna lord and the Moon, Tajika aspects, Ithasala, Easarapha and Kamboola between the Lagna lord, the significator and the Moon, and the category's own stanzas. Each indicator has its rule, what the chart shows, whether it fired and its source; then an equal-weight tally, the II.5-8 success grade and the II.10-12 timing. No prediction text.

[Group: Vedic] [Endpoint: POST /v1/vedic/prashna/analysis] [Required: date, time, latitude, longitude, category] [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>",
      "category": "<category>"
    },
    "name": "astroway_vedic_prashna_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate of the question, YYYY-MM-DD, local.
timeYesTime of the question, HH:mm:ss, local.
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
numberNoA number 1-108 from the querent: its navamsa fixes the Arudha sign. Send arudhaSign or number, not both. KP's 1-249 number is /v1/vedic/kp/horary.
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
categoryYesThe subject of the question: relationship, career, travel, lost-item, litigation, general. It picks the house of the question and its lord (the significator). Health is not offered.
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.
longitudeYes
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
arudhaSignNoArudha: the sign (1 Aries .. 12 Pisces) of the direction the querent faces or the square of the chakra the querent touches (Prasna Marga II.7-11). Omit it and the Udaya Lagna stands in for it (IX.30-31).
ayanamsaIdNo
sphutaGulikaNoWhich point enters Trisphuta. mandi (default): the Prasna Marga author takes Gulika by the Mandi ghatika method (translator's note to V.14-16). gulika: the end of Saturn's eighth part.
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
moonNo
chartNo
lagnaNo
notesNo
tallyNo
methodNo
timingNo
sourcesNo
categoryNo
indicatorsNo
significatorNo
successGradeNo
houseOfQuestionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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/openWorld=false, so the description is free to add output semantics, which it does well: each indicator carries rule, chart observation, fired flag and source, followed by an equal-weight tally, a II.5-8 success grade and II.10-12 timing. It also discloses a behavioral boundary ('No prediction text') and that health categories are refused. What it does not disclose is any failure mode or cost handling (the 20-credit cost sits in context, not the description).

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?

Purpose is front-loaded in the opening clause and the second half is devoted to return contents, with no filler. The first sentence is a long technical run-on dense with Sanskrit terms (Ithasala, Easarapha, Kamboola), which costs readability but each clause carries information an agent cannot get from the schema.

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

Completeness4/5

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

For a 14-parameter, 20-credit analytical endpoint with an output schema and full annotations, the description covers purpose, per-category scoping, refusal of health and the shape of results. The residual gaps are sibling routing and the fact that inputs describe the moment of the question rather than a birth moment, both of which an agent may need before choosing this tool over its neighbours.

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

Parameters3/5

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

Schema description coverage is 79%, so the schema already documents date/time/latitude/longitude, the category enum, ayanamsa, timezone, arudhaSign, number, sparse fields and precision. The description adds only the meaning of `category` (it picks the house of the question and its lord, the significator) and the health exclusion. That is real but marginal added meaning over the schema, matching the baseline 3.

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?

Names a specific verb+resource: Prasna Tantra indicators for one category, enumerating the houses, lords, Tajika aspects, Ithasala/Easarapha/Kamboola and the per-category stanzas it returns. The scope ('one category', 'No prediction text') is precise. It stops short of naming or contrasting the siblings that overlap most (astroway_vedic_prashna_chart, astroway_vedic_prashna_number, astroway_horary_horary, astroway_vedic_kp_horary), so disambiguation is left to the agent.

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 tool answers a yes/no horary question when a category (relationship, career, travel, lost-item, litigation, general) applies. The one explicit exclusion is health ('health is refused'), which is useful. No alternative tool is named for cases where a raw Prashna chart is wanted, and no prerequisite (that date/time/place must be the moment of the question) is stated here.

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