Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Praśna (horary): a question, a deal, or a horary number

get_prashna
Read-onlyIdempotent

Use this when the user asks a specific question and wants it answered from the moment of asking rather than from a birth chart — "will this deal close?", "will I recover?", "will I find what I lost?" — or when an astrologer gives a horary number 1–249. Send where the user is as place; it is never defaulted. The chart of the moment and place a question is asked, read on classical praśna rules, no model. Always: the praśna lagna and its lord, the Moon, the house of the matter asked about, the classical rules that apply (recovery from illness for a health question; recovery of a lost article when the question names one), and the further classical rules that held on this chart, each with its reference and the chart facts that made it hold. With deal: the deal praśna — significators (lagna lord = you, 7th = the other side, 10th = the undertaking, 11th = gain), their planetary contacts, the grounds for and against, and an ordered verdict (perfects, perfects after obstacles, contested, delayed, delayed and contested, not perfected); add birthData for the natal commitment calendar beside it, never blended with it. With horaryNumber (1–249): the horary table — house cusps for the moment that number rises, planets at the moment of judgment, their ruling lords, and the ruling planets; no judgment is asserted from it. Rules about caste, prenatal sex or death timing are withheld and counted. Cost: 3 credits per call (only successful calls are charged; a sandbox key is free and returns a fixed sample). Deterministic: the same input always gives the same answer. Example arguments: {"place":{"latitude":28.6139,"longitude":77.209,"timezone":"Asia/Kolkata","label":"New Delhi"},"askedAt":"2026-10-14T10:30:00+05:30","question":"Will the supply contract with Northwind be signed?","deal":{"label":"Northwind supply contract","kind":"contract","signingDate":"2026-11-02"},"birthData":{"date":"1990-05-12","time":"14:35","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209},"horaryNumber":108}

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": {
      "place": "<place>"
    },
    "name": "get_prashna"
  }
}

Input Schema

NameRequiredDescriptionDefault
dealNoRead the question as one deal (the deal praśna).
placeYesWhere the question is asked. Required: a praśna cast at the wrong longitude is a different chart.
domainNoWhat the question is about: picks the house of the matter and scopes the classical rules. With a deal and no domain, the deal's own.
askedAtNoThe instant the question was asked, ISO 8601 with Z or an offset. Default: now. Send this or askedAtLocal, not both.
questionNoThe question in the user's words. Gates the lost-article dictum; it does not choose the domain.
birthDataNoOnly with `deal`, and with a birth time: the querent's natal commitment calendar is set beside the praśna for the signing date.
askedAtLocalNoThe wall clock at the place when the question was asked, YYYY-MM-DDTHH:mm, read in place.timezone.
horaryNumberNoA horary number (1–249): adds the horary table.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"What the question is about: picks the house of the matter and scopes the book rules. With a deal and no domain, the deal's own."New value: +"What the question is about: picks the house of the matter and scopes the classical rules. With a deal and no domain, the deal's own."
    • changedInput schema / properties / horaryNumber / description
      Previous value: -"A KP horary number: adds the KP horary table."New value: +"A horary number (1–249): adds the horary table."
    • changedOutput schema / $defs / PrashnaResponse / properties / deal / description
      Previous value: -"The deal praśna, when `deal` was sent: deal, lagna, moon (with its last and next Tājika contacts and void of course), significators, contacts, grounds, verdict, natalCrossCheck (null without birthData), notEncoded, method."New value: +"The deal praśna, when `deal` was sent: deal, lagna, moon (with its last and next planetary contacts and void of course), significators, contacts, grounds, verdict, natalCrossCheck (null without birthData), notEncoded, method."
    • changedOutput schema / $defs / PrashnaResponse / properties / kpHorary / description
      Previous value: -"The KP horary table, when `horaryNumber` was sent: {computed: true, data: {horaryNumber, cuspMomentIso, judgmentMomentIso, latitudeValidated, cusps, planets, rulingPlanets, notComputed}} or {computed: false, reason}."New value: +"The horary table, when `horaryNumber` was sent: {computed: true, data: {horaryNumber, cuspMomentIso, judgmentMomentIso, latitudeValidated, cusps, planets, rulingPlanets, notComputed}} or {computed: false, reason}."
    • changedOutput schema / $defs / PrashnaResponse / properties / prashna / properties / bookRules / description
      Previous value: -"Rules from the praśna books that held on this chart."New value: +"Further classical praśna rules that held on this chart."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the safety profile is covered; the description still adds non-obvious behaviour: 3 credits per call with only successful calls charged, a free sandbox key returning a fixed sample, and full determinism. It also discloses an ethical constraint that no annotation could carry — caste, prenatal-sex and death-timing rules are withheld and counted — and states the horary table asserts no judgment. Loses a point only for not flagging latency or the response envelope.

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?

Front-loaded correctly: trigger, then output shape, then cost, then example arguments. Dense but almost every clause carries information. It slips into long run-on sentences in the second paragraph (significators, contacts, grounds, verdicts, natal calendar all in one breath), which costs a point against a genuinely complex tool.

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

Completeness5/5

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

An output schema exists, yet the description still tells the agent enough to choose the tool correctly: what the default reading contains, what each optional input adds, what is deliberately withheld, and what a call costs. Nothing an agent needs before invoking an 8-parameter nested-schema tool is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns more by explaining what each optional parameter *produces* rather than what it is: `deal` yields significators, contacts, grounds for and against, and an ordered verdict list; `horaryNumber` yields the horary table; `birthData` adds a natal calendar "beside it, never blended with it". It also stresses that `place` is never defaulted, which is a usage rule the schema only half-states.

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?

Names a specific verb and resource — cast the chart of the moment and place a question is asked, read on classical praśna rules — and immediately contrasts it with the birth-chart route, which is exactly the distinction an agent needs against get_chart and the other natal tools. The three usage shapes (plain question, deal, horary number) are stated up front.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use this when the user asks a specific question and wants it answered from the moment of asking rather than from a birth chart" gives an explicit trigger and an explicit exclusion, backed by three sample questions. It then routes between variants: `deal` for a deal praśna, `horaryNumber` when an astrologer supplies a number 1–249, `birthData` only beside a deal.

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.