Skip to main content
Glama
IPGeolocation

IP Geolocation MCP Server

by IPGeolocation
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Astronomy Time Series

get_astronomy_time_series
Read-only

Retrieve daily sunrise, sunset, moonrise, moonset, and moon phase data for any location over a date range up to 90 days.

Instructions

Read-only daily astronomy series via GET /v3/astronomy/timeSeries. Works on free and paid plans. Cost: 1 credit per request. Use for date ranges up to 90 days; use get_astronomy for one date or real-time sun/moon position.

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 caller 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 must be 0-10000 meters. 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 cache and makes a fresh upstream request only when the user asks.

Input Schema

TableJSON 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). 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 (0-10000). 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. 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.

Tool Definition Quality

A5/5.0
Behavior5/5

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

Disclosures beyond annotations: cost, selector priority, that lang is paid-only (returns 401 on free plans), force_refresh bypasses cache and consumes credits. No contradiction with readOnlyHint=true.

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?

Four sentences front-loading purpose and usage, then returns structure, then parameter details. No redundant information; every sentence serves a purpose.

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 10 parameters, no output schema, the description covers overall purpose, return structure (location, astronomy array with fields), parameter semantics, constraints, and alternative tools. Complete for agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds essential meanings: date format YYYY-MM-DD and 90-day max, lat/long must be together, elevation range, time_zone changes timestamp formatting, lang effect on non-English, force_refresh only when user asks.

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 explicitly states it is a read-only daily astronomy series via GET endpoint, and distinguishes from sibling tool 'get_astronomy' for one date or real-time. Specific verb 'get' and resource 'astronomy time series'.

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?

Clearly indicates when to use this tool (date ranges up to 90 days) versus 'get_astronomy' (one date/real-time). Also mentions cost (1 credit per request), selector priority, and parameter constraints like 90-day max range.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IPGeolocation/ipgeolocation-io-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server