Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Ascendant, MC and house cusps

get_ephemeris_angles
Read-onlyIdempotent

Use this when you need the ascendant, midheaven or house cusps for a moment and place. Ascendant, midheaven and twelve cusps for a moment and place. Placidus is undefined beyond the polar circles at some moments; the call then returns 422 houses_undefined_at_latitude. 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":"1990-05-12T14:35:00+05:30","latitude":28.6139,"longitude":77.209,"houseSystem":"placidus"}

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>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_ephemeris_angles"
  }
}

Input Schema

NameRequiredDescriptionDefault
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).
latitudeYesGeographic latitude in decimal degrees, north positive.
longitudeYesEast positive.
houseSystemNoHouse system for the cusps: whole_sign (default), equal or placidus.whole_sign

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial extra context on top: the 422 houses_undefined_at_latitude failure mode beyond the polar circles, the pricing model (0.1 credit, billed in blocks of 10, only successful calls charged, free sandbox key), and determinism. These are exactly the operational facts annotations cannot express.

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 trigger condition is front-loaded and the pricing/error/determinism lines are each one sentence. The first two sentences overlap almost verbatim in content, which is the one wasteful element, but the block is short and scannable.

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 6-parameter, enum-heavy tool with an output schema and full annotation coverage, the description covers the remaining agent-facing risks: the latitude edge case, the error code, billing behavior and a concrete example invocation. Nothing needed to call it 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 earns an extra point because the worked example arguments demonstrate the expected ISO 8601 offset format, decimal-degree coordinates and the houseSystem value that interacts with the Placidus caveat. It does not explain zodiac/ayanamsa interplay beyond what the schema enums already say.

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 the exact resource returned: ascendant, midheaven and twelve house cusps for a moment and place. That is specific enough to distinguish it from get_ephemeris_positions and get_ephemeris_ayanamsa by subject matter, though it never explicitly contrasts itself with those siblings.

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 the ascendant, midheaven or house cusps" gives a clear trigger condition, and the Placidus/latitude caveat tells the caller when the call will fail. There is no explicit statement of when to prefer a sibling tool instead, so it stops short of a 5.

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.