Skip to main content
Glama
RyanCardin15

noaa-tidesandcurrents-mcp

get_high_tide_flooding_annual

Retrieve annual high tide flooding counts for a specific station based on station ID, date range, flood threshold, and output format. Use this tool to analyze coastal flood data from NOAA Tides and Currents.

Instructions

Get high tide flooding annual count data for a station

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
begin_dateNoStart date (YYYYMMDD format)
datumNoDatum reference for DPAPI
end_dateNoEnd date (YYYYMMDD format)
formatNoOutput format (json, xml, csv)
stationYesStation ID
thresholdNoFlood threshold level
year_rangeNoYear range (YYYY-YYYY format)

Implementation Reference

  • Core handler method in DpapiService that constructs and fetches data from NOAA DPAPI '/htf/annual' endpoint using shared fetchDpapi utility.
    async getHighTideFloodingAnnual(params: Record<string, any>): Promise<any> {
      const { station, format = 'json', ...rest } = params;
      
      return this.fetchDpapi('/htf/annual', {
        station,
        format,
        ...rest
      });
    }
  • MCP tool registration block that defines the tool name, description, input schema, and execute handler wrapping the service call.
    server.addTool({
      name: 'get_high_tide_flooding_annual',
      description: 'Get high tide flooding annual count data for a station',
      parameters: HighTideFloodingAnnualSchema,
      execute: async (params) => {
        try {
          const result = await dpapiService.getHighTideFloodingAnnual(params);
          return JSON.stringify(result);
        } catch (error) {
          if (error instanceof Error) {
            throw new Error(`Failed to get high tide flooding annual data: ${error.message}`);
          }
          throw new Error('Failed to get high tide flooding annual data');
        }
      }
    });
  • Zod schema defining the input parameters for the tool, including station, format, datum, threshold, date ranges, and year range.
      station: StationSchema,
      format: FormatSchema,
      datum: DpapiDatumSchema,
      threshold: ThresholdSchema,
      begin_date: z.string().optional().describe('Start date (YYYYMMDD format)'),
      end_date: z.string().optional().describe('End date (YYYYMMDD format)'),
      year_range: YearRangeSchema
    }).describe('Get high tide flooding annual count data');
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 the tool 'gets' data, implying a read-only operation, but doesn't disclose other traits such as rate limits, authentication needs, data format defaults, or what happens with missing parameters. This leaves significant gaps for a tool with 7 parameters and no output schema.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero waste, making it easy to parse quickly.

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 complexity (7 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return values, data structure, or behavioral context needed for effective use. While the schema covers parameters well, the lack of output details and behavioral transparency makes this inadequate for a data retrieval tool with multiple siblings.

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 description adds no parameter semantics beyond what the input schema provides. With 100% schema description coverage, the schema already documents all 7 parameters thoroughly, including enums and formats. The description doesn't compensate by explaining interactions between parameters (e.g., how 'year_range' relates to 'begin_date'/'end_date'), so it meets the baseline of 3.

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

Purpose3/5

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

The description states the tool retrieves 'high tide flooding annual count data for a station', which is clear but vague about the specific verb and scope. It distinguishes from siblings like 'get_high_tide_flooding_daily' by specifying 'annual', but doesn't fully differentiate from other flooding tools like 'get_high_tide_flooding_projections' or 'get_high_tide_flooding_likelihoods' in terms of data type or use case.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, context for choosing annual data over daily/monthly/seasonal flooding data, or comparisons to other flooding-related tools in the sibling list. Usage is implied by the name but not elaborated.

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'

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