Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

Sun & moon times

sun_times
Read-onlyIdempotent

Gives the sun and moon times for a place on one day: first light, dawn, sunrise, the end of morning golden hour, solar noon, evening golden hour, sunset, dusk, night, moonrise and moonset, with the moon's phase, the next full and new moon, and the next equinox or solstice. Times are computed for the place and said in its own time zone. A day an event does not happen there (a polar day or night) says so. Read only; sets nothing.

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": {
      "place": "<place>"
    },
    "name": "sun_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day, "2026-11-02". Left out, today at the place.
placeYesA city, park, beach or address, "Lisbon" or "Yosemite". Coordinates as "38.72, -9.14" work too.
your_time_zoneNoThe person's own IANA time zone, to say each time on their clock too when it differs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond this: times are computed for the place, rendered in its own time zone, and polar day/night events are explicitly reported as not happening.

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?

Front-loaded with the core purpose, followed by the useful output enumeration, time-zone note, edge-case note, and safety note. Every sentence contributes information an agent needs.

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?

For a read-only lookup tool with no output schema, the description is complete: it lists the returned events, explains local time zone handling, covers polar-day/night edge cases, and confirms no state is changed.

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 description coverage is 100%, so the schema already documents place, date, and your_time_zone. The description reinforces that place/date drive the computation and time zone output, but adds no syntax or format detail beyond the schema.

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?

States a specific verb and resource: gives sun and moon times for a place on a day. The enumerated outputs and the closing 'Read only; sets nothing' distinguish it from alarm-setting siblings such as set_sun_alarm.

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

Usage Guidelines4/5

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

Provides clear context that this is a read-only lookup for astronomical times, implicitly contrasting with mutation/alarm tools. It does not explicitly name an alternative or state when not to use it, which keeps it below a 5.

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

All LFG Alarm 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