Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Sunrise Sunset

SunriseSunset
Read-only

Sunrise Sunset: Sunrise Sunset calculates exact sunrise and sunset times, twilight stages, and golden hour windows for any latitude and longitude coordinates. Paid plans can specify custom dates and receive solar noon. With local=true, the response names the IANA timezone of the coordinates on any plan, and paid plans also get each time in local time with its UTC offset. (Cost: 2 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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "SunriseSunset"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesThe latitude of the location
lonYesThe longitude of the location
dateNoThe date for which you want to get the sunrise and sunset times (e.g., MM-DD-YYYY : 01-01-2022)
localNoAlso return the timezone of the coordinates and every time in local time

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds value on top: plan-tier gating for the date parameter and solar noon, the differential behavior of local=true between free and paid plans, and the 2-credit cost. That is meaningful operational context an agent would not get from annotations alone.

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?

Dense but well-structured: capability first, plan limitations second, local behavior third, cost last in parentheses. The opening 'Sunrise Sunset: Sunrise Sunset' restates the name/title redundantly, which is the only real waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value detail is not required, and the description covers plan limits, cost, and the local-flag behavior. Minor gaps remain: what happens when date is omitted (presumably current date) and any coordinate validity bounds.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description does add plan-gating meaning for date and clarifies that local=true yields an IANA timezone on any plan but offset-qualified local times only on paid plans — modest but genuine meaning beyond the schema's simpler phrasing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: calculates sunrise and sunset times, twilight stages, and golden hour windows for lat/lon coordinates. It is clearly distinct from generic siblings, though it never names the overlapping alternatives (SunPosition, MoonriseMoonset, DaylightDurationCalculator) that an agent would have to disambiguate against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies when to reach for it (you have coordinates and want solar event times) and flags that custom dates require a paid plan, which is a real usage precondition. But there is no explicit when-not guidance and no routing to the closely related solar/time siblings, so selection still requires inference.

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

All APIVerve toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources