Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Ayanamsa values

get_ephemeris_ayanamsa
Read-onlyIdempotent

Use this when you need an ayanamsa value at a moment. The ayanāṁśa (the sidereal offset) at a moment, for each supported ayanāṁśa (mean, without nutation). 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-06T00: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": {
      "datetime": "<datetime>"
    },
    "name": "get_ephemeris_ayanamsa"
  }
}

Input Schema

NameRequiredDescriptionDefault
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).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, but the description goes well beyond them: an explicit cost model (0.1 credit, billed per started block of 10, only successful calls charged, free sandbox key returning a fixed sample) and a determinism guarantee. The parenthetical "mean, without nutation" also discloses a precision caveat an agent could not infer from annotations or schema.

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?

The usage trigger is front-loaded and each subsequent line carries distinct information (definition, cost, determinism, example). There is minor redundancy between "when you need an ayanamsa value at a moment" and "The ayanāṁśa at a moment", but nothing is padded.

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, so return values need no explanation, and annotations carry the safety profile. The description fills the remaining gaps an agent needs before calling: cost/billing, determinism, and the mean-without-nutation precision caveat, all against a single fully documented parameter.

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 coverage is 100% and the datetime property already documents the ISO 8601 format, the 1800-01-02 to 2149-12-31 UTC range, and the invalid_datetime refusal. The description adds only a worked example argument, which is mildly useful but does not extend the semantics beyond the schema — baseline 3 applies.

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?

The description names a specific resource (the ayanāṁśa / sidereal offset) and a specific scope (at a moment, for each supported ayanamsa, mean without nutation), which is enough to distinguish it from get_ephemeris_positions and get_ephemeris_angles. It does not explicitly contrast itself with those siblings, but the resource noun is unambiguous.

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 an ayanamsa value at a moment" gives a clear selection condition and is front-loaded. There are no stated exclusions or named alternatives for cases where a sibling (e.g. positions or angles) would be the better call, so it stops short of full routing guidance.

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.