Skip to main content
Glama
IPGeolocation MCP Server

IPGeolocation MCP Server

Astronomy Time Series

get_astronomy_time_series
Read-only

Fetch daily sunrise, sunset, moonrise, moonset, twilight, and moon phase data for a date range up to 90 days by coordinates, location, or IP.

Instructions

Read-only daily astronomy series via GET /v3/astronomy/timeSeries. Works on free and paid plans. Cost: 1 credit per request. This endpoint covers date ranges up to 90 days; get_astronomy provides one-date and real-time sun/moon data.

Returns { location, astronomy: [...] } with one daily item per date containing sunrise/sunset, moonrise/moonset, twilight blocks, day_length, sun/moon status, and moon_phase. Selector priority is lat/long, location, ip, then the server's public egress IP when no selector is provided.

dateStart and dateEnd are required YYYY-MM-DD values with a maximum 90-day span. lat and long must be provided together; elevation is in meters, with a maximum of 10000; negative values are treated as 0. time_zone changes timestamp formatting to include full dates. lang only changes location fields; non-English lang is paid-only and returns 401 on free plans. force_refresh bypasses cached data, makes a new upstream request, and can consume credits.

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": {
      "dateStart": "<dateStart>",
      "dateEnd": "<dateEnd>"
    },
    "name": "get_astronomy_time_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoIPv4 or IPv6 address to get astronomy data for that IP's location.
latNoLatitude coordinate. Highest priority. Must be used with long.
langNoResponse language for location fields in IP-based lookups (en, de, ru, ja, fr, cn, es, cs, it, ko, fa, pt, ar). Paid plans only. Free plan returns 401 for non-English languages.
longNoLongitude coordinate. Must be used with lat.
dateEndYesEnd date in YYYY-MM-DD format. Required. Maximum range between dateStart and dateEnd is 90 days.
locationNoCity or address string (e.g. San Francisco, CA).
dateStartYesStart date in YYYY-MM-DD format. Required. Maximum range between dateStart and dateEnd is 90 days.
elevationNoElevation in meters above sea level. Maximum 10000; negative values are treated as 0. Affects sunrise/sunset calculations.
time_zoneNoIANA timezone name to express times in (e.g. America/New_York). If set, time fields include full date instead of just time.
force_refreshNoDefault false. When true, bypasses cached astronomy time-series data; a successful refresh makes a new upstream request and can consume credits.

Output Schema

NameRequiredDescriptionDefault
dataNoPresent on success: API result after field selection, redaction, and transport limits.
pageNo
errorNoPresent on failure, with isError: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.4
    • changedInput schema / properties / elevation / description
      Previous value: -"Elevation in meters above sea level (0-10000). Affects sunrise/sunset calculations."New value: +"Elevation in meters above sea level. Maximum 10000; negative values are treated as 0. Affects sunrise/sunset calculations."
  2. Changed2 schema fields changedv2.0.3
    • removedOutput schema / properties / data / additionalProperties / anyOf
      Removed value: -[
      -  {
      -    "type": "null"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "array"
      -  },
      -  {
      -    "type": "object"
      -  }
      -]
    • addedOutput schema / properties / data / additionalProperties / type
      Added value: +[
      +  "null",
      +  "boolean",
      +  "number",
      +  "string",
      +  "array",
      +  "object"
      +]
  3. Addedv2.0.1
  4. Removedv2.0.0
  5. Changed1 schema field changedv1.0.15
    • changedInput schema / properties / force_refresh / description
      Previous value: -"Default false. Leave unset unless the user asks to refresh or rerun."New value: +"Default false. Set true only when the user asks to refresh cached astronomy time-series data; a successful refresh makes a new upstream request and can consume credits."
  6. First observedv1.0.10

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses cost per request, that force_refresh bypasses cache, makes an upstream request, and can consume extra credits, and that non-English lang returns 401 on free plans. It also documents the selector fallback chain ending in the server's public egress IP, which is behavior no annotation or schema field exposes.

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?

Front-loaded with route, plan, and cost, then return shape, then selector priority, then parameter caveats – a sensible progression. It runs long and a couple of clauses (e.g. restating elevation and time_zone details already in the schema) could be trimmed without loss.

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 ten parameters, a paid-tier gate, and caching behavior, the description covers the cost, plan, selector resolution, and refresh semantics an agent must know before invoking. With an output schema present, the brief return-shape note is sufficient rather than required.

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 most parameter meaning is already structured; however, the description adds the selector priority order (lat/long, location, ip, egress IP fallback) that appears nowhere in the schema. Remaining parameter notes restate schema text (90-day span, elevation clamp, time_zone formatting), so it is strong but partly duplicative.

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?

States a specific verb and resource (daily astronomy series), the HTTP route, and immediately contrasts with get_astronomy as the single-date/realtime alternative. An agent can distinguish it from every listed sibling 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 Guidelines5/5

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

Explicitly routes the agent: use this for ranges up to 90 days, use get_astronomy for one-date and real-time data. It also names plan eligibility (free and paid) and the credit cost, which are exactly the selection conditions an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.