Skip to main content
Glama

AstroWay Astrology API (full catalogue)

Time zone and UTC offset at a point

astroway_geo_timezone
Read-onlyIdempotent

The IANA zone at a point and the UTC offset its clocks kept at that local date and time, from the tz database, never a fixed offset: Kyiv answers +2 in January, +3 in July and +4 on 15 May 1990, when it kept Moscow summer time. time defaults to 12:00 and matters on the day clocks change; a skipped hour resolves to the offset from before the change, a repeated one to its first occurrence. standardOffset is the smaller of the year's offsets and isDst is true when the clock is ahead of it.

[Group: Astro-Geography] [Endpoint: GET /v1/geo/timezone] [Required: lat, lon] [Cost: 5 credits (Tier ½)]

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "astroway_geo_timezone"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude in decimal degrees, north positive.
lonYesLongitude in decimal degrees, east positive.
dateNoLocal calendar date `YYYY-MM-DD` at the point. Defaults to today (UTC).
timeNoLocal clock time `HH:MM` or `HH:MM:SS`. Matters only on the day clocks change.12:00
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

NameRequiredDescriptionDefault
dateNo
timeNo
isDstNo
latitudeNo
nauticalNo
timezoneNo
longitudeNo
utcOffsetNo
utcOffsetTextNo
standardOffsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds substantive behavioral detail beyond annotations: tz database sourcing, never using a fixed offset, DST transition resolution rules for skipped and repeated hours, and the meanings of `standardOffset` and `isDst`.

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?

The description is front-loaded with the core definition, then adds only relevant DST and output-field semantics. The example and edge-case rules are dense but each sentence earns its place for a timezone lookup tool.

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?

Given the output schema, 100% parameter description coverage, and rich annotations, the description is complete enough to invoke the tool correctly. It covers the subtle temporal behavior and output-field meanings without needing to repeat schema details.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful semantics for `time`, including its noon default and that it matters on clock-change days, plus DST edge-case resolution; it does not discuss `fields` or `precision`, but those are fully documented in the schema.

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?

The description states a specific resource and scope: the IANA zone and UTC offset its clocks kept at a point and local date/time, sourced from the tz database, explicitly not a fixed offset. The Kyiv example reinforces that this is historical DST-aware timezone lookup, distinguishing it from a simple fixed-offset conversion.

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

Usage Guidelines3/5

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

The description explains how the tool behaves on DST boundaries and what `time` defaults to, but it does not explicitly say when to use this tool versus alternatives or name sibling tools. Usage is implied by the purpose rather than guided.

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