Skip to main content
Glama
RyanCardin15

LocalTides MCP Server

get_sun_times_range

Retrieve sunrise, sunset, and other sun event times for a specific date range and location using latitude, longitude, and timezone. Output available in JSON or text format.

Instructions

Get sun rise/set and other sun event times for a date range and location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateYesEnd date (YYYY-MM-DD format)
formatNoOutput format (json or text)
latitudeYesLatitude for location-specific calculations
longitudeYesLongitude for location-specific calculations
start_dateYesStart date (YYYY-MM-DD format)
timezoneNoTimezone for the results. Defaults to UTC.

Implementation Reference

  • Core implementation of getSunTimesRange that computes sun times over a date range using SunCalc library, looping daily and calling getSunTimes.
    getSunTimesRange(params: SunTimesRangeParams): SunTimesInfo[] {
      const startDate = new Date(params.start_date);
      const endDate = new Date(params.end_date);
      
      if (isNaN(startDate.getTime()) || isNaN(endDate.getTime())) {
        throw new Error('Invalid date format. Please use YYYY-MM-DD format.');
      }
      
      if (startDate > endDate) {
        throw new Error('Start date must be before end date.');
      }
      
      const result: SunTimesInfo[] = [];
      const currentDate = new Date(startDate);
      
      while (currentDate <= endDate) {
        result.push(this.getSunTimes({
          date: currentDate.toISOString().split('T')[0],
          latitude: params.latitude,
          longitude: params.longitude,
          timezone: params.timezone
        }));
        
        // Move to next day
        currentDate.setDate(currentDate.getDate() + 1);
      }
      
      return result;
    }
  • Zod schema definition for the input parameters of the get_sun_times_range tool.
    export const SunTimesRangeParamsSchema = z.object({
      start_date: z.string().describe('Start date (YYYY-MM-DD format)'),
      end_date: z.string().describe('End date (YYYY-MM-DD format)'),
      latitude: z.number().min(-90).max(90).describe('Latitude for location-specific calculations'),
      longitude: z.number().min(-180).max(180).describe('Longitude for location-specific calculations'),
      format: z.enum(['json', 'text']).optional().describe('Output format (json or text)'),
      timezone: z.string().optional().describe('Timezone for the results. Defaults to UTC.')
    });
    
    export type SunTimesRangeParams = z.infer<typeof SunTimesRangeParamsSchema>;
  • MCP tool registration for 'get_sun_times_range', including description, input schema reference, and execute handler that delegates to SunService.
    server.addTool({
      name: 'get_sun_times_range',
      description: 'Get sun rise/set and other sun event times for a date range and location',
      parameters: SunTimesRangeParamsSchema,
      execute: async (params) => {
        try {
          const results = sunService.getSunTimesRange(params);
          if (params.format === 'text') {
            let text = `Sun times from ${params.start_date} to ${params.end_date} at latitude ${params.latitude}, longitude ${params.longitude}:\n\n`;
            
            results.forEach(result => {
              text += `Date: ${result.date}\n`;
              text += `Sunrise: ${result.sunrise || 'N/A'}\n`;
              text += `Sunset: ${result.sunset || 'N/A'}\n`;
              text += `Day length: ${Math.floor(result.dayLength / 60)}h ${Math.round(result.dayLength % 60)}m\n\n`;
            });
            
            return text;
          }
          return JSON.stringify(results);
        } catch (error) {
          if (error instanceof Error) {
            throw new Error(`Failed to get sun times range: ${error.message}`);
          }
          throw new Error('Failed to get sun times range');
        }
      }
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions what the tool returns ('sun rise/set and other sun event times') but lacks behavioral details: no information about rate limits, authentication requirements, error conditions, or what constitutes 'other sun event times.' The description doesn't disclose whether this is a read-only operation or has any side effects.

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, efficient sentence that front-loads the core purpose. Every word earns its place: 'Get' (action), 'sun rise/set and other sun event times' (resource), 'for a date range and location' (scope). No wasted words or redundant phrasing.

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

Completeness3/5

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

Given 6 parameters with 100% schema coverage and no output schema, the description is minimally adequate. It covers the what (sun event times) and scope (date range, location) but lacks behavioral context needed when annotations are absent. For a tool with no annotations and no output schema, it should ideally mention return format expectations or error handling, but the concise purpose statement meets basic requirements.

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 all parameters thoroughly. The description adds minimal value beyond the schema by implying date-range and location parameters, but doesn't provide additional context like format examples, timezone behavior beyond the default, or what 'other sun event times' might include. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description clearly states the tool's purpose: 'Get sun rise/set and other sun event times for a date range and location.' It specifies the verb ('Get'), resource ('sun rise/set and other sun event times'), and scope ('for a date range and location'). However, it doesn't explicitly differentiate from sibling tools like 'get_sun_times' or 'get_next_sun_event', which appear related.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With multiple sun-related sibling tools (get_sun_times, get_next_sun_event, get_sun_position), there's no indication of when this range-based tool is preferred over single-date or next-event queries. No prerequisites, exclusions, or comparative context are mentioned.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RyanCardin15/NOAA-TidesAndCurrents-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server