Skip to main content
Glama

Aviation & Space Weather Data (Tanod)

sun_moon_times

Read-onlyIdempotent

skypeek: Get sunrise, sunset, twilight, moonrise and moon phase for a place and date. For satellite passes use satellite_passes. Returns sunrise, sunset, solar noon, day length and civil / nautical / astronomical twilight, plus moonrise, moonset, moon phase, illumination and distance, for a point and a local date, in a time zone you choose. Computed locally (Meeus series; no upstream call): sun and twilight times within about 1 minute, moonrise and moonset within about 3 minutes; sea-level horizon, terrain and weather not modelled. A bad date or time zone is a 422 (not charged). Typically under 0.2 s. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/sunrise-sunset-moon-phase-api.html

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": "sun_moon_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA time zone for the date and the output (such as Asia/Manila); default UTC.
latYesLatitude in degrees (-90 to 90).
lonYesLongitude in degrees (-180 to 180).
dateNoLocal date YYYY-MM-DD (1900-2100); default today.

Output Schema

NameRequiredDescriptionDefault
tzNo
latNo
lonNo
sunNo
dateNo
moonNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
methodNo
accuracyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / date / default
      Removed value: -null
    • removedInput schema / properties / date / title
      Removed value: -"Date"
    • removedInput schema / properties / lat / title
      Removed value: -"Lat"
    • removedInput schema / properties / lon / title
      Removed value: -"Lon"
    • removedInput schema / properties / tz / default
      Removed value: -null
    • removedInput schema / properties / tz / title
      Removed value: -"Tz"
    • removedInput schema / title
      Removed value: -"sun_moon_timesArguments"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "accuracy": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "date": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "lat": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "lon": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "method": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "moon": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "sun": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "tz": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations (readOnly/idempotent/non-destructive) by disclosing that computation is local with no upstream call, accuracy bounds (~1 min sun/twilight, ~3 min moonrise/moonset), that sea-level horizon applies and terrain/weather are not modelled, that invalid date or time zone yields an uncharged 422, typical latency under 0.2 s, and the price plus free-tier limit. These are exactly the operational facts an agent needs to decide and budget a call.

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

Conciseness3/5

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

Front-loading is good and much of the content is high-value, but the return list is effectively stated twice — once in the opening sentence and again in the 'Returns sunrise, sunset, solar noon...' sentence — which is redundant given an output schema exists. Pricing, free tier, and docs link are useful but add density to an otherwise single-block description.

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 four-parameter read-only computation tool, the definition covers accuracy, error behavior, cost, latency, and limits, and an output schema exists so return shape need not be re-explained. Nothing an agent needs in order to call this correctly or budget for it is missing.

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 description coverage is 100%, so lat/lon/date/tz are already fully documented, and the description adds only framing ('for a point and a local date, in a time zone you choose'). No extra detail such as tz format edge cases or coordinate rounding is provided beyond the schema, so this lands at the baseline.

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?

Opens with a specific verb and a concrete enumeration of the resources returned (sunrise, sunset, twilight, moonrise, moon phase) for a place and date, and explicitly separates itself from the sibling satellite_passes. An agent can classify the tool without opening the 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?

Names the alternative tool for a nearby need ('For satellite passes use satellite_passes') and establishes defaults (date defaults to today, tz defaults to UTC), which tells the agent it can call with only lat/lon. It stops short of stating exclusions such as historical/future validity windows in prose, but the required-parameter contract is clear.

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.