Moonrise & Moonset Grounding DataMoonrise & Moonset Grounding Data

OnlineCredit Usage:1 per callTool:MoonriseMoonsetGroundingData

The tool

Ground agents in verifiable moonrise, moonset and phase data so location-aware lunar answers rest on real astronomy, not approximation.

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

Tool call
{
  "name": "MoonriseMoonsetGroundingData",
  "arguments": {
    "lat": "37.7749",
    "lon": "-122.4194"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about 37.7749 in the terms this source covers is enough for it to reach for MoonriseMoonsetGroundingData on its own.

Connecting

One server URL covers every source 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.

Client config
{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervecontext.com/v1/mcp

Per-client setup — Claude Desktop, 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.

ArgumentTypeExampleDescription
latRequirednumber37.7749The latitude of the location
lonRequirednumber-122.4194The longitude of the location
datePremiumstring01-16-2026The date to get the moonrise and moonset times for (MM-dd-yyyy)

What the model gets back

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

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "coordinates": {
      "latitude": 37.7749,
      "longitude": -122.4194
    },
    "phase": "Waning Crescent",
    "moonrise": "2025-12-16T12:24:41.532Z",
    "moonset": "2025-12-16T22:22:04.027Z",
    "moonAlwaysUp": false,
    "moonAlwaysDown": false
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
coordinatesobject{…}
coordinates.latitudenumber37.7749Latitude coordinate of the specified location
coordinates.longitudenumber-122.4194Longitude coordinate of the specified location
phasePremiumstringWaning CrescentCurrent moon phase at specified time and location
moonrisestring2025-12-16T12:24:41.532ZISO 8601 timestamp when moon rises at location
moonsetstring2025-12-16T22:22:04.027ZISO 8601 timestamp when moon sets at location
moonAlwaysUpPremiumbooleanfalseIndicates if moon is always above horizon
moonAlwaysDownPremiumbooleanfalseIndicates if moon is always below horizon

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value with a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at moonrise: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This source isn't part of VerveContext. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use Moonrise & Moonset Grounding Data

Set up Moonrise & Moonset Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext 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.APIVerveReference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKitReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →

Frequently asked questions

Do I have to tell the agent to use MoonriseMoonsetGroundingData?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveContext catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?