Docs/Skills/Planet Positions Skill

Planet Positions Skill

Get planet positions data

OperationalCredits 2 per callp50 285msAstrology

Overview

Pass observer latitude, longitude, and a chosen planet from Pluto to the Moon. The API calculates observation geometry with optional observer altitude and observation time, returning whether the target sits below the local horizon. Paid plans let you set specific dates and return right ascension, declination, distances, sidereal time, and Cartesian position vectors.

Live Test Planet Positions Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as PlanetPositionsSkill. 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": "PlanetPositionsSkill",
  "arguments": {
    "lat": "37.7749",
    "lon": "-122.4194",
    "planet": "mars"
  }
}

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 PlanetPositionsSkill 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.

ArgumentTypeDescription
dateOptionalPremiumstringThe date to get planetary position data for (MM-DD-YYYY)
date
timeOptionalstringThe time of day for the calculation (HH:mm format, 24-hour). Defaults to 00:00 if not provided
time
latRequirednumberThe latitude of the observer
range -90–90
lonRequirednumberThe longitude of the observer
range -180–180
altOptionalnumberThe altitude of the observer in meters
range 0–∞
planetRequiredstringThe planet to get position data for
sunmoonmercuryvenusmarsjupitersaturnuranus+2

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": {
    "planet": "Moon",
    "isBelowHorizon": false,
    "date": "2025-04-15T10:37:00Z",
    "observer": {
      "latitude": 37.7749,
      "longitude": -122.4194
    },
    "rightAscension": {
      "hours": 15,
      "minutes": 13,
      "seconds": 11
    },
    "declination": {
      "degrees": -23,
      "minutes": 10,
      "seconds": 56
    },
    "distance": {
      "km": 402457.36,
      "lightTravelSeconds": 1.342,
      "astronomicalUnits": 0.003
    },
    "siderealTime": {
      "hours": 16,
      "minutes": 2,
      "seconds": 42
    },
    "hourAngle": {
      "hours": 0,
      "minutes": 49,
      "seconds": 31
    },
    "vectors": {
      "x": -0.0016452947779903913,
      "y": -0.0018463324771434563,
      "z": -0.0010590407236111441
    }
  }
}

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.

FieldTypeExampleDescription
planetstringMoonName of the celestial body being observed
isBelowHorizonbooleanfalseWhether the planet is below horizon at observation location
datestring2025-04-15T10:37:00ZObservation date and time in ISO 8601 format
observerobject{…}The location the position was calculated for
observer.latitudenumber37.7749Observer latitude in decimal degrees
observer.longitudenumber-122.4194Observer longitude in decimal degrees
rightAscensionPremiumobject{…}Right ascension coordinates of the planet
rightAscension.hoursPremiumnumber15Right ascension hours component (0-23)
rightAscension.minutesPremiumnumber13Right ascension minutes component (0-59)
rightAscension.secondsPremiumnumber11Right ascension seconds component (0-59)
declinationPremiumobject{…}Declination coordinates of the planet
declination.degreesPremiumnumber-23Declination degrees component (-90 to 90)
declination.minutesPremiumnumber10Declination minutes component (0-59)
declination.secondsPremiumnumber56Declination seconds component (0-59)
distancePremiumobject{…}Distance to the planet in various units
distance.kmPremiumnumber402457.36Distance to planet in kilometers
distance.lightTravelSecondsPremiumnumber1.342Light travel time in seconds from planet
distance.astronomicalUnitsPremiumnumber0.003Distance in astronomical units (AU)
siderealTimePremiumobject{…}Local sidereal time at observation
siderealTime.hoursPremiumnumber16Local sidereal time hours component (0-23)
siderealTime.minutesPremiumnumber2Local sidereal time minutes component (0-59)
siderealTime.secondsPremiumnumber42Local sidereal time seconds component (0-59)
hourAnglePremiumobject{…}Hour angle from the meridian
hourAngle.hoursPremiumnumber0Hour angle hours component from meridian
hourAngle.minutesPremiumnumber49Hour angle minutes component from meridian
hourAngle.secondsPremiumnumber31Hour angle seconds component from meridian
vectorsPremiumobject{…}Position vector components
vectors.xPremiumnumber-0.0016452947779903913X component of planet position vector
vectors.yPremiumnumber-0.0018463324771434563Y component of planet position vector
vectors.zPremiumnumber-0.0010590407236111441Z component of planet position vector

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.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This skill is not part of VerveKit. Check the catalog.
429Out 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

Stargazing Tour Scheduling
When planning evening viewing sessions, astronomy guides check if target planets sit below the horizon at their field camp location and scheduled observation time.
Telescope Mount Pointing
Astrophotographers on paid plans calculate exact right ascension and declination coordinates to aim automated tracking mounts toward visible solar system targets.
Astrology Chart Generation
Natal chart software queries planetary bodies across specific dates on paid plans to map celestial positions for birth chart generation.
Planetarium Display Sync
To project accurate night sky exhibits, science museum kiosks query live planetary coordinates based on local building coordinates and viewing time.

Other ways to use Planet Positions Skill

Set up Planet Positions 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 →

More in Astrology:

Was this page helpful?