Skip to main content
Glama
RyanCardin15

LocalTides MCP Server

get_current_predictions

Retrieve current and tide predictions for specific stations using station ID, date range, and customizable parameters like time zone, units, and output format on LocalTides MCP Server.

Instructions

Get current predictions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
begin_dateNoStart date (YYYYMMDD or MM/DD/YYYY)
binNoBin number
dateNoDate to retrieve data for ("today", "latest", "recent", or specific date)
end_dateNoEnd date (YYYYMMDD or MM/DD/YYYY)
formatNoOutput format (json, xml, csv)
intervalNoInterval (MAX_SLACK or a number for minutes)
rangeNoNumber of hours to retrieve data for
stationYesStation ID
time_zoneNoTime zone (gmt, lst, lst_ldt)
unitsNoUnits to use ("english" or "metric")
vel_typeNoVelocity type (speed_dir or default)

Implementation Reference

  • The core handler function that executes the tool logic by fetching current predictions data from the NOAA API using the appropriate product parameter.
    async getCurrentPredictions(params: Record<string, any>): Promise<any> {
      return this.fetchDataApi({
        ...params,
        product: 'currents_predictions'
      });
    }
  • Zod schema defining the input parameters and validation for the get_current_predictions tool.
    export const GetCurrentPredictionsSchema = z.object({
      station: StationSchema,
      date: DateSchema,
      begin_date: BeginDateSchema,
      end_date: EndDateSchema,
      range: RangeSchema,
      bin: BinSchema,
      interval: z.string().optional().describe('Interval (MAX_SLACK or a number for minutes)'),
      vel_type: z.enum(['speed_dir', 'default']).optional().describe('Velocity type (speed_dir or default)'),
      units: UnitsSchema,
      time_zone: TimeZoneSchema,
      format: FormatSchema,
    }).refine(
      data => (data.date || (data.begin_date && data.end_date) || (data.begin_date && data.range) || (data.end_date && data.range) || data.range),
      { message: "You must provide either 'date', 'begin_date' and 'end_date', 'begin_date' and 'range', 'end_date' and 'range', or just 'range'" }
    );
  • Registration of the get_current_predictions tool in the custom McpServer class, specifying name, description, input schema, and handler that delegates to NoaaService.
    const getCurrentPredictions: MCPTool = {
      name: "get_current_predictions",
      description: "Get current predictions",
      inputSchema: GetCurrentPredictionsSchema,
      handler: async (params) => {
        return this.noaaService.getCurrentPredictions(params);
      }
    };
  • Alternative registration of the get_current_predictions tool using FastMCP server.addTool, with inline schema and execute handler calling NoaaService.
    server.addTool({
      name: 'get_current_predictions',
      description: 'Get current predictions',
      parameters: z.object({
        station: StationSchema,
        date: DateSchema,
        begin_date: BeginDateSchema,
        end_date: EndDateSchema,
        range: RangeSchema,
        bin: BinSchema,
        interval: z.string().optional().describe('Interval (MAX_SLACK or a number for minutes)'),
        vel_type: z.enum(['speed_dir', 'default']).optional().describe('Velocity type (speed_dir or default)'),
        units: UnitsSchema,
        time_zone: TimeZoneSchema,
        format: FormatSchema,
      }).refine(refineDateParams, { message: dateRefinementMessage }),
      execute: async (params) => {
        try {
          const result = await noaaService.getCurrentPredictions(params);
          return JSON.stringify(result);
        } catch (error) {
          if (error instanceof Error) {
            throw new Error(`Failed to get current predictions: ${error.message}`);
          }
          throw new Error('Failed to get current predictions');
        }
      }
    });
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Get current predictions' reveals nothing about authentication requirements, rate limits, data freshness, whether this is a read-only operation, what format the predictions come in, or any other behavioral characteristics. This is completely inadequate for a tool with 11 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with just three words, this represents under-specification rather than effective conciseness. The description fails to convey essential information that would help an AI agent understand and use the tool correctly, making it inefficient despite its brevity.

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

Completeness1/5

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

Given the complexity (11 parameters, 1 required), lack of annotations, no output schema, and 22 sibling tools, the description is completely inadequate. It doesn't explain what 'predictions' means, what domain this operates in, how results are structured, or when to use this versus alternatives. This fails to provide the minimal context needed for effective tool selection.

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?

The schema description coverage is 100%, with all 11 parameters well-documented in the schema itself. The description adds zero additional parameter information beyond what's already in the schema. According to the rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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

Purpose2/5

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

The description 'Get current predictions' is a tautology that restates the tool name without adding meaningful context. It doesn't specify what type of predictions (tide, weather, etc.), what resource they apply to, or how this differs from sibling tools like 'get_tide_predictions' or 'get_currents'.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance on when to use this tool versus the many sibling tools available. With 22 sibling tools including similar-sounding ones like 'get_tide_predictions' and 'get_currents', the lack of any differentiation or context makes this score a 1.

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