Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Positions at a moment

get_ephemeris_positions
Read-onlyIdempotent

Use this when you need where the Sun, Moon and planets are at a moment (sidereal or tropical), not a reading. Sun, Moon, planets and lunar nodes at one moment: longitude, latitude, distance, speed and retrograde flag, with sign, and nakṣatra and its quarter when sidereal. equatorial: true adds apparent right ascension and declination. Cost: 0.1 credit per call, billed as 1 credit per started block of 10 Ephemeris calls (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: {"datetime":"2026-10-06T06:00:00Z","bodies":["Sun","Moon","Mars","Jupiter","Saturn","TrueNode"],"zodiac":"sidereal","ayanamsa":"lahiri"}

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": {
      "datetime": "<datetime>"
    },
    "name": "get_ephemeris_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodiesNoDefault: all twelve.
zodiacNosidereal (default) or tropical.sidereal
ayanamsaNoSidereal only.lahiri
datetimeYesISO 8601 with Z or an explicit offset, between 1800-01-02 and 2149-12-31 UTC. A time without a zone is refused (invalid_datetime).
equatorialNoAlso return apparent right ascension and declination. Default false.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / bodies / items / description
      Previous value: -"MeanNode and TrueNode are Rāhu (mean or true); Ketu is the node + 180°."New value: +"MeanNode and TrueNode are Rāhu (mean or true); Ketu is the node + 180°. Every AstroNest chart, reading and timing endpoint uses the mean node."
    • changedOutput schema / $defs / EphemerisBody / description
      Previous value: -"MeanNode and TrueNode are Rāhu (mean or true); Ketu is the node + 180°."New value: +"MeanNode and TrueNode are Rāhu (mean or true); Ketu is the node + 180°. Every AstroNest chart, reading and timing endpoint uses the mean node."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses a per-call cost model (0.1 credit, billed in blocks of 10, only successful calls charged, free sandbox key returning a fixed sample) and states determinism. Annotations already cover the read-only/idempotent safety profile, and the description adds the billing and determinism facts an agent cannot get anywhere else.

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 use case, then output contents, cost, determinism and an example — a sensible ordering with no filler sentences. The cost sentence is long and the example block is verbose, but both carry information an agent needs before calling.

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 read-only, deterministic computation tool with an output schema and 100% schema coverage, everything needed to call correctly is present: trigger, sidereal/tropical behavior, cost implications for repeat calls, and a worked example. Return values are covered by the output schema, so no gap remains.

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 structured fields already carry baseline meaning; the description still adds return-shape semantics ('nakṣatra and its quarter when sidereal') and a concrete example argument object that shows realistic body lists and sidereal usage. It largely restates the equatorial and zodiac semantics already in the schema, so it stops short of a 5.

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?

States a specific verb and resource — 'where the Sun, Moon and planets are at a moment (sidereal or tropical)' — and explicitly rules out a reading, which separates it from the interpretive siblings like get_life_reading or get_chart. It does not, however, distinguish itself from the other ephemeris siblings (get_ephemeris_angles, get_ephemeris_series, get_ephemeris_sunrise, get_ephemeris_ayanamsa), so an agent still has to infer the split.

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 you need ... not a reading' gives a clear positive trigger and one negative exclusion. The gap is that no named alternative is offered for the adjacent ephemeris tools (series vs. single moment vs. angles), which is exactly the decision an agent faces 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.