Skip to main content
Glama
Sign In
TimezoneToolkit MCP Server

TimezoneToolkit MCP Server

by Cicatriiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

calculate_sunrise_sunset

Retrieve sunrise, sunset, and twilight times for any location and date. Supply latitude, longitude, and timezone to obtain exact astronomical times.

Instructions

Calculate sunrise, sunset, and twilight times for a specific location and date

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "calculate_sunrise_sunset"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate for calculation (ISO string or natural language). Defaults to current date.
latitudeYesLatitude of the location (-90 to 90)
timezoneNoIANA timezone name (e.g., 'Europe/Paris'). Defaults to UTC.
longitudeYesLongitude of the location (-180 to 180)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what is calculated but does not mention output format, timezone handling, or twilight definitions. The schema notes defaults, but the description adds no behavioral context.

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?

The description is a single, front-loaded sentence with a direct action verb and no unnecessary words. It is appropriately concise.

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

Completeness2/5

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

Given the absence of both annotations and an output schema, the description is underspecified. An agent cannot determine what the return value looks like, whether times are localized, or what twilight encompasses, making the tool incomplete in context.

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% with descriptions for all four parameters. The description adds no additional parameter semantics beyond generic references to 'location and date', so it relies on 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?

The description uses a specific verb (Calculate) and names the exact outputs (sunrise, sunset, twilight times) plus scope (specific location and date). This clearly distinguishes it from sibling tools like calculate_moon_phase or convert_time.

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?

Context implies this tool is for astronomical time calculations, but there is no explicit guidance on when to use it versus alternatives. No exclusions or sibling tool references are provided, so usage is only implied.

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

Deploy Server

Other Tools