Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Positions over a range

get_ephemeris_series
Read-onlyIdempotent

Use this when you need planetary positions across a range of dates, for a transit table or to find when a planet changes sign or stations. Positions from start to end (inclusive) every stepMinutes, for transit tables and station finding. At most 1,000 points (too_many_points beyond). A 365-point daily table costs 4 credits. Cost: 1 credit per started 100 points (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: {"start":"2026-10-01T00:00:00Z","end":"2026-10-10T00:00:00Z","stepMinutes":1440,"bodies":["Mercury","Venus"]}

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": {
      "start": "<start>",
      "end": "<end>",
      "stepMinutes": "<stepMinutes>"
    },
    "name": "get_ephemeris_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesISO 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).
startYesISO 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).
bodiesNoDefault: all twelve.
zodiacNosidereal (default) or tropical.sidereal
ayanamsaNoSidereal only.lahiri
stepMinutesYesMinutes between points (1 to 525,600). At most 1,000 points per call.

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?

Annotations already cover safety and idempotency, yet the description still adds the 1,000-point cap with its error code (too_many_points), per-100-point credit pricing, the fact that only successful calls are charged, sandbox behavior, and determinism. That is genuinely useful context an agent cannot get from the annotations.

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 with the trigger condition, limits, and cost in a compact block. There is mild redundancy between the first and second sentences (both restate the range/step behavior), which keeps it from a perfect score.

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?

Covers the trigger, the sampling semantics, hard limits, error code, pricing model, sandbox behavior, and determinism. An output schema exists, so return values need not be explained — nothing an agent needs to call this 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; the description goes further by explaining that points are inclusive from start to end at stepMinutes intervals and by supplying a realistic example argument object that shows how the fields compose.

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 ('planetary positions across a range of dates') plus the concrete use cases (transit table, sign changes, stations). The range framing implicitly separates it from get_ephemeris_positions, but 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 Guidelines4/5

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

'Use this when you need planetary positions across a range of dates, for a transit table or to find when a planet changes sign or stations' gives a clear selection context. It stops short of naming the alternative endpoint for a single moment, so the when-not side is left to inference.

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.