Moon Position Skill

Overview

A moon and lunar position API. Moon Position works by analyzing the location provided and calculating moon position data. It uses advanced algorithms to calculate data such as altitude, azimuth, and distance of the moon from the location and returns the moon position data.

Live Test Moon Position Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as MoonPositionSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "MoonPositionSkill",
  "arguments": {
    "lat": "37.7749",
    "lon": "-122.4194"
  }
}

You do not name the tool yourself; the model picks it. Asking about 37.7749 in the terms this skill covers is enough for it to reach for MoonPositionSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`lat`Required	number	The latitude of the location range -90–90
`lon`Required	number	The longitude of the location range -180–180
`date`OptionalPremium	string	The date to get the moon position data for (MM-dd-yyyy) date
`time`Optional	string	The time of day for the calculation (HH:mm format, 24-hour). Defaults to 00:00 if not provided time
`timezone`Optional	string	IANA timezone name the date and time are given in. Defaults to the timezone of the supplied coordinates timezone

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "date": "01-22-2026",
    "time": "14:30",
    "coordinates": {
      "latitude": 37.7749,
      "longitude": -122.4194
    },
    "moon": {
      "altitude": -0.407908976399288,
      "azimuth": 1.4720499058762104,
      "distance": 404332.6834067969
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`date`	string	`01-22-2026`	The date for which moon position was calculated
`time`	string	`14:30`	The time of observation in HH:MM format
`coordinates`	object	`{…}`	The observation location the position was calculated for
`coordinates.latitude`	number	`37.7749`	The latitude coordinate of the observation location
`coordinates.longitude`	number	`-122.4194`	The longitude coordinate of the observation location
`moon`	object	`{…}`	The moon's position as seen from the observation location
`moon.altitude`	number	`-0.407908976399288`	Moon altitude above the horizon in radians, calculated from observation location. Negative values mean the moon is below the horizon
`moon.azimuth`Premium	number	`1.4720499058762104`	Moon azimuth in radians, derived astronomical calculation
`moon.distance`Premium	number	`404332.6834067969`	Distance from observer to moon in kilometers

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Night Photography Planning: Landscape photographers check moon altitude across evening hours to time foreground illumination and align night-sky shots.
Telescope Pointing Assistants: Amateur astronomy software plots lunar elevation by observer coordinates to guide telescope targeting during backyard stargazing sessions.
Coastal Night Navigation: When planning coastal night voyages, marine navigation tools track lunar altitude to anticipate natural visibility over open water.
Nocturnal Wildlife Research: Field biology platforms log lunar elevation against animal GPS tracks to correlate predator hunting patterns with ambient moonlight.

Other ways to use Moon Position Skill

Set up Moon Position Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →