Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Classical techniques for a chart

get_techniques
Read-onlyIdempotent

Use this when the user or an astrologer asks for a specific classical computation — planetary strength, transit point tables, another life-period timeline, the annual chart, house cusps, a named yoga, the birth pañcāṅga, Manglik, house lords and aspects — rather than for a reading. Pass sections to fetch only what is needed. The computed classical working for a chart, no model: strength scores for each planet and house, point tables for transit support, further life-period timelines with the periods running at referenceDate, the full planetary-period ladder, the annual chart for the year running at referenceDate, house-cusp and ruling-planet tables, classical yogas, special ascendants and aspects, the natal pañcāṅga, house lords with planetary aspects, Manglik (Kuja doṣa) with its exceptions, and what would change under another ayanāṁśa. Each section is {computed: true, data} or {computed: false, reason} — a technique that cannot be computed for this chart (for example without a birth time) says why and the rest still return. No verdicts, scores or lifespan figures. 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: {"birthData":{"date":"1990-05-12","time":"14:35","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209},"sections":["shadbala","dashas","panchanga"],"referenceDate":"2026-10-14T00:00:00Z"}

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": {
      "birthData": "<birthData>"
    },
    "name": "get_techniques"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionsNoReturn only these sections. Default: all.
birthDataYesThe person's birth data: date, local time (omit if unknown), IANA timezone, latitude and longitude.
residenceNoWhere the person lives; the annual chart is cast for this place. Defaults to the birthplace.
referenceDateNoISO date or datetime for the running periods and the annual chart's year. Defaults to now.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / referenceDate / description
      Previous value: -"ISO date or datetime for the running periods and the Varṣaphal year. Defaults to now."New value: +"ISO date or datetime for the running periods and the annual chart's year. Defaults to now."
    • changedInput schema / properties / residence / description
      Previous value: -"Where the person lives; the Varṣaphal is cast for this place. Defaults to the birthplace."New value: +"Where the person lives; the annual chart is cast for this place. Defaults to the birthplace."
    • changedOutput schema / $defs / TechniquesResponse / properties / techniques / description
      Previous value: -"One entry per requested section. `dashas` holds ashtottari, kalachakra, narayana, yogini and chara, each a section."New value: +"One entry per requested section. `dashas` holds the further life-period timelines, each a section."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses per-section {computed: true, data} / {computed: false, reason} graceful degradation, gives the missing-birth-time example, states 'No verdicts, scores or lifespan figures', and adds cost (3 credits, successful calls only, free sandbox key) and determinism. These are exactly the traits an agent needs before calling a paid computational endpoint.

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-loads the selection rule ('Use this when...') before the feature enumeration, and the cost/determinism lines are short and useful. The long mid-paragraph list of computations is dense and slightly redundant with the section enum, but it earns its place as a what-is-included manifest.

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?

For a 4-param tool with nested birthData and an output schema, the description covers the trigger condition, per-section failure semantics, cost model, and the consequence of omitting birth time. Nothing an agent needs to decide or invoke correctly 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 adds real meaning: it maps section names to content (strength scores, point tables, the planetary-period ladder, cusps, yogas, Manglik with exceptions, ayanāṁśa variant) and clarifies that referenceDate drives the running periods and the annual chart's year. It also reinforces the default-to-all behavior of `sections`.

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+resource ('the computed classical working for a chart') and enumerates the concrete computations returned (strength scores, point tables, life-period timelines, annual chart, cusps, yogas, pañcāṅga, Manglik). Explicitly distinguishes itself from reading tools with 'rather than for a reading', so an agent can separate it from get_life_reading, get_guidance, etc. without opening a schema.

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

Usage Guidelines4/5

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

'Use this when the user or an astrologer asks for a specific classical computation ... rather than for a reading' gives a clear positive trigger and a negative one. It does not name the specific sibling tools that handle readings/interpretations, so the agent must map 'a reading' onto get_life_reading itself. Still strong, actionable context.

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.