Skip to main content
Glama

AstroNest — Vedic Astrology Readings

Sunrise and sunset

get_ephemeris_sunrise
Read-onlyIdempotent

Use this when you need sunrise and sunset for a date and place, or where the Vedic day begins. Sunrise, sunset and the next sunrise for a local date and place: upper limb at the sea-level horizon with 36.6′ refraction. The Vedic day runs from sunrise to the next sunrise. 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: {"date":"2026-10-06","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209}

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": {
      "date": "<date>",
      "timezone": "<timezone>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_ephemeris_sunrise"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesLocal calendar date, YYYY-MM-DD.
latitudeYesGeographic latitude in decimal degrees, north positive.
timezoneYesIANA name, e.g. Asia/Kolkata. Defines the local day.
longitudeYesEast positive.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost and billing mechanics (0.1 credit/call, 1 credit per started block of 10, only successful calls charged, sandbox key free with a fixed sample) and determinism. It also pins the astronomical convention (upper limb, sea-level horizon, 36.6′ refraction), which materially affects result interpretation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the use case, then the precise definition, then cost, then determinism, then an example — each line carries distinct information an agent needs. No filler sentences or restatement of the title.

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; the description still covers accuracy conventions, the Vedic-day extension of the result, pricing, and sandbox behavior. 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 adds a concrete worked argument set showing date/timezone/latitude/longitude together, which clarifies expected formats and units in practice. It does not add semantics for any individual parameter beyond the schema, so not a 5.

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?

Names the exact resource and output set: 'Sunrise, sunset and the next sunrise for a local date and place', plus the Vedic-day concept it also answers. This is clearly separable from the other ephemeris siblings (positions, angles, ayanamsa, series) 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?

Opens with an explicit trigger: 'Use this when you need sunrise and sunset for a date and place, or where the Vedic day begins.' That is a clear use context, though it names no exclusion or alternative sibling for adjacent needs (e.g. planetary positions).

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.