Skip to main content
Glama

AstroWay Core astrology

Sun Times

astroway_western_sun_times
Read-onlyIdempotent

Calculate sunrise, sunset, twilight times, and day length for a given date and geographic location.

[Group: Core] [Endpoint: POST /v1/sun-times] [Required: date, latitude, longitude] [Cost: 10 credits (Tier 1)]

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

Input Schema

NameRequiredDescriptionDefault
dateYes
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
longitudeYes
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
dawnNo
duskNo
sunsetNo
sunriseNo
dayLengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedInput schema / properties / latitude / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / latitude / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedInput schema / properties / longitude / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / longitude / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / dawn / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / dawn / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / dayLength / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / dayLength / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / dusk / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / dusk / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / sunrise / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / sunrise / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / sunset / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / sunset / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description's bracketed metadata does add genuinely new behavioral context not present in annotations: the POST /v1/sun-times endpoint and a per-call cost of 10 credits (Tier 1). It says nothing about what is returned or how twilight bands are defined, but with a rich output schema that gap is tolerable.

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?

One front-loaded sentence states the capability, followed by a dense bracketed block of operational facts. Nothing is padded, though the "Required: date, latitude, longitude" line merely restates the schema and is the one item that does not fully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not explain return values, and the tool is a straightforward read-only calculation over seven parameters whose non-obvious ones are documented in the schema. The only real omission is that nothing signals the precedence between timezone and timezoneOffset at the description level, which is left to the parameter docs.

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 57%: timezone, timezoneOffset, fields and precision carry detailed descriptions, while date (pattern only) and latitude/longitude have none. The description contributes only the framing that latitude/longitude constitute the "geographic location" and that date selects the day; it does not explain the timezone versus timezoneOffset precedence or the compact-mode parameters, so it neither compensates for nor worsens the partial coverage. 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 verb ("Calculate") and an enumerated resource ("sunrise, sunset, twilight times, and day length"), plus the two dimensions of input (date, geographic location). No sibling tool in the list covers solar rise/set times, so an agent can identify this uniquely even though the description never explicitly contrasts with neighbors like astroway_calendar_moon_phase.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to reach for this tool versus alternatives, no prerequisites, and no exclusions. The only guidance is implicit in the phrase "for a given date and geographic location"; the agent must infer everything else from the name and the bracketed metadata.

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.

Resources